Guys,
This wasn't my point.
I'm not discouraging regular releases - I think that's great.
I had a problem with there being 10 issues in JIRA not getting any attention before a release. Vincent didn't have time to fix it (which we can all relate to), and the single feature in the release was more important than I realised, so I have no problem with the particular release.
I'm definitely saying we should release more often, but also that we should try and fix more outstanding bugs each time too.
Cheers, Brett
Felipe Leme wrote:
On Wed, 2004-10-13 at 05:02, Vincent Massol wrote:
Ideally yes, I agree with you. But if we do in our current state (i.e.
committers involved, etc), it'll never happen. Or it will but only once a
I agree with Vincent. It's really frustrating when the CVS code has something you need, but it takes months for a new release of the software to be officially rolled out.
What I do find extremely important is to make it clear what is in the
release. And this we're doing nicely with both the changes report and the
announcement plugin. It's not like we're telling users we've fixed
everything and they find it's not true.
That's true. Maybe we could improve the process just a little bit, by adding a 'known bugs' category for the changes.xml report.
-- Felipe
--------------------------------------------------------------------- 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]
