Create a stable branch or version tags about cssmin HOT 14 CLOSED

👍 The original repo has several versions: https://code.google.com/p/cssmin/downloads/list

from cssmin.

Yes, the repository should have annotated tags.

You can of course branch for development purposes, but users shouldn't consume or use branches as releases. Branches will always contain moving code. If you depend on a branch, you are basically shooting yourself to leg. It is going to misfire. Any library that doesn't use tags, is basically useless, no matter how great the codebase is - until it starts to use tags.

The original repository has no concrete tagged releases, so you can't replicate those, neither does this repository reflect its history. This repository, isn't its clone and for what ever reason, hosts the build fragment of CSSmin rather than the individual source files. Rather strange decision.

The fact that the original SVN doesn't have releases, doesn't really surprise me, considering that CSSMin never really used the SVN. Oh, well the project predates autoloaders, phars and packages. The repository itself was more of a file dump and a wiki.

from cssmin.

👍

from cssmin.

+1

If it's of any use to anybody we've forked this and added a stable version tag: https://github.com/messagedigital/CssMin

from cssmin.

+1 !

from cssmin.

I'm on it, sorry for the delay :-)

from cssmin.

I hope I did correctly.
https://github.com/natxet/CssMin/releases
Please tell me if I made something wrong.
Thanks!

from cssmin.

Thanks @natxet!

hehe, and @gocom if you shoot yourself in the leg, and it misfires, then that's probably a good thing.

;-)

from cssmin.

Thanks!

from cssmin.

😍

from cssmin.

I think it would be a good idea to tag a new version, since there are couple of useful bugfixes in dev version.

from cssmin.

ping @natxet

from cssmin.

+1 @natxet

from cssmin.

Very sorry for the delay. Did create 3.0.3

from cssmin.