Actually, another problem we have is that we tend to be too focused on our own development ideas and ignore those non-committer patches for just too long... we should make an effort and consider these with high(-ish) priority.
Just an opinion.
-- Salut,
Jordi.
En/na [EMAIL PROTECTED] ha escrit:
On 6 Feb 2004 at 1:36, Jordi Salvat i Alabart wrote:
Remember ESR's moto in CATB? "Release Early, Release Often": http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html
We should make an effort in this sense and try to have at least monthly point releases -- weekly even better. Call them beta if you wish...
I would agree with this, in spirit. I think that the 2.0 release should be followed up with weekly releases of bug fixes we make on the 2.0 branch, for at least 3-4 weeks. Once it's settled, I don't think actual releases of development stuff is served well by weekly, or even monthly releases. If we were 20 developers working all the time, I might say different, but we're 2-3 right now doing active coding, and it seems a bit much to expect there's something worth releasing every month.
So far, JMeter's been averaging a pretty steady 6-month release schedule for about 3 years.
It might be nice to push that to a 3-month interval instead. That seems workable and useful. It might be nice to lay it out in a roadmap on the website
-- Michael Stover [EMAIL PROTECTED] Yahoo IM: mstover_ya ICQ: 152975688 AIM: mstover777
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
