Blueprint versions
Matthew Nuzum
> Well just to assuage your fears, I'll mention that we haven't changed
> anything since 0.71, Olav's last committed version
> For the whole list, please understand, Blueprint 0.71 is a working,
> useful framework at a usable & stable version, which you can get from
> Google Code, the official Blueprint repo.
Then we should call "0.71" Blueprint 1.0.
By the way, most open source projects do version numbers like this:
"0.x.y". Therefore the next step after 0.71 would be 0.72, 0.73, etc.
Kind of like after 0.9 comes 0.10 and 0.11. A point release on the 0.7
branch would be 0.7.1.
I know that's not the system blueprint has used in the past, 0.6 was
followed by 0.7 and the point release was 0.71, but that is confusing
to people since it breaks from convention.
If 0.71 is a stable release and the current developers are not
maintaining future versions then now is probably the perfect time to
adopt a conventional versioning system. By calling the first version
in the git branch 1.0, which is identical to 0.71 then we're saying to
people, "this is a stable version you can use and count on." (which is
factual)
This also allows the use of standard conventions for development and
testing versions and then future stable versions. So minor
enhancements bump the version to something like 1.1 or 1.2, major
changes bump it to 2.0.
--
Matthew Nuzum
newz2000 on freenode
Horst Gutmann
when I look at the filename :-)
http://blueprintcss.googlecode.com/files/Blueprint%200.7.1.zip