cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Fedotov" <>
Subject Re: update cocoon-2.0.2.tar.gz / .zip?
Date Wed, 03 Apr 2002 10:20:28 GMT

> I already thought that the third number is for bugfix
> releases. The second number is for introducing new
> feature and maybe backward incompatability issues.

Yes, I remember. The difference is that I propose to do
that on regular basis. I've polished my ideas a bit, here
they are:

1. If there is any major bugfix, schelule new release for
_two days_ after that bug was fixed. If no new issues were
found in two days, release new version.

2. If there is really alot of serious bugfixes, release
just once a week or two. Is such thing happens, it means
that original release was made too early.

3. If there were just minor bugfixes like samples etc, put
them into corresponding cvs branch as before, and that's
it. No need in new release. Instructions on how to get that
version from cvs should be available on website, as well as
changes done after the last release.


To unsubscribe, e-mail:
For additional commands, email:

View raw message