Am Freitag, den 09.06.2006, 14:10 -0400 schrieb Noel J. Bergman: > Stefano Bagnara wrote: > > > James is a top level project and we didn't publish any release > > versioning scheme, so we can simply vote and do what we voted. > > +1 > > And I'll be happy to see Vincenzo's code dropped into v2.3 when we release > it. The logic I apply is that it is not a core change, but optional > matchers/mailets, so if there is a bug, there is no risk to most users.
Right. But i whould like to see it in trunk first to maybe vote for include in branch.. > > > we make 1 release every 2 years > > I'd like that to change, though. I would not mind seeing a minor release > every two months or so, primarily adding bug fixes, minor improvements, and > matchers/mailets to a major release. And I would not mind seeing a major > release once or twice per year, so long as we have the new material and it > has been vetted as sufficiently qualitative to stamp our approval on it. Yeah like i said before.. We should focus to make a major release every 6 month. Bugfix releases should be made if we think we need it. > > This is why I make an issue about release management. Not to stop work, but > to try to separate longer term, risky, changes from what can go into the > next near-term release. This is why we need to specify an roadmap! bye Norman
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
