"Carsten Ziegeler" <[EMAIL PROTECTED]> writes: > I would like to a add one more point: Most of us do not care about > releasing new versions. We *must* come back to release often - release > early. But each time, we try to get a new version out, someone comes > up and says: Wait XYZ is not finished/working/discussed right now, > we should first get this working. Or even worse, someone starts something >and leaves it in an uncomple > Stefano Mazzocchi wrote: > > Now, to your points: > > > | never commit code that depends on non-released stuff | > > > I really would agree to this policy, if it is possible to follow. Now, in > theory that sounds really great and easy, but in practice it's near to > impossible. Think of the problems for example we had months/years > ago with severe bugs in Xalan or Xerces. We had to use the latest > CVS in order to get Cocoon running as the released stuff was not > working. > And what does released mean? One could argue that an alpha version > is a released version ;) > I would like to relax the policy a little bit to: > Never release a stable version that depends on non-released stuff (where > released version has to be at least stable in API).
If I followed the policy of not relying on non-released stuff, I would be limited to coconn 2.0.4 :-(. While I feel muche more comfortable with release stuff, that't not a option for me. I would be very glad to see a 2.1 release soon. Martin -- Martin Holz <[EMAIL PROTECTED]> Softwareentwicklung / Vernetztes Studium - Chemie FIZ CHEMIE Berlin Franklinstrasse 11 D-10587 Berlin
