On Wed, 3 Apr 2002, Mikhail Fedotov wrote: > Hi! > > > I could make a release on Friday, Monday or Tuesday if > > the problems are fixed by then. > > Let me introduce some useful idea about making new > releases. > > You can do one stable branch like "2.0.2" and severa > bugfixes branches like "2.0.2.1" and apply only bugfixes > there. If two day passed since last bugfix and no one finds > problems about it, when it's time for "2.0.2.x".
I already thought that the third number is for bugfix releases. The second number is for introducing new feature and maybe backward incompatability issues. Giacomo > > This way you can improve stability. Look at this cite: > > ****** > Cocoon does not work properly on the RaQ4i server. It > crashes the Tomcat server > which in turns crashes the Apache server. There are Cobalt > customised automated > Tomcat scripts on the server to take into consideration. > ****** > > I don't know that version of cocoon/tomcat (and that > scripts) that guy was talking about, but (weekly?) bugfix > releases might help with such things much better than new > releases filled with new features and bugs just once in a > month or two. Code freeze doesn't help enough as we've > seen. > > Mikhail > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, email: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
