-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm kind of amazed to even think about this right now, but...
We're about a month in to 3.0.4 and 2 weeks in to 4.0.2 and, at present we have the following statistics (from JIRA - http://issues.apache.org/jira/secure/BrowseProject.jspa?id=10573&subset=-1): 3.0.5 - ----- 10 issues resolved Issues are primarily code related 4.0.3 - ----- 42 issues resolved Issues are primarily documentation related I'd like to look at one of two options for both releases: 1. Go through JIRA marking "Fix Version" to the appropriate release for any issues we want resolved in the next release (instead of setting 'Fix Release' at the time the issue is resolved) -- or -- 2. Start planning the release of these two so we can move on to the next release cycle. I know there are still a few documentation issues for 4.0.3, but I'm in no way saying "stop here". I just wanted to point out that we've gotten some issues resolved and we need to be looking at what else should go into the next release without pushing it out months from now. [I was thinking "plan on releasing end of May", but that's just going by "what we have fixed already" + "about two months between minor releases"] The benefit to putting "Fix Version" in prior to resolution is that it allows the Road Map feature of JIRA to provide an 'at a glance' view of what's done and what remains to be done for a specific release. Problem is... it doesn't work unless we all make it work. *pleading* Brian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) iD8DBQFEUP/qaCoPKRow/gARAuSyAJ9lqYyr5tUKOcKeCx26VYRhWLazewCgrI3S 2Bt9swaH5+RcQ/Uruz887r4= =S/7s -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
