-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 lol - actually? yep, sure did - April 13. That quick-fix release to add a backward compatible Form interface method. Before that was Mar 31 for 4.0.1. I figure if we can roadmap issues for 3.0.5 and 4.0.3 that can be fixed/tested by end of May we can get on a "couple month" release cycle - - give or take. I think this is often enough to be responsive and not so often users can't keep up.
Have to toss kudos over to Andy as well - wouldn't be as close as we are without his help. We'll try to keep up what's out there - you keep going with 5 :-) Howard Lewis Ship wrote: > Did 4.0.2 ever get released? > > BTW ... I'm thrilled at the great effort you and Jesse have been > putting in to these releases! > > On 4/27/06, Brian K. Wallace <[EMAIL PROTECTED]> wrote: > 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) iD8DBQFEUWwXaCoPKRow/gARApfJAKDahQ/oPvKcXsDpHKUTPp3f56brWQCgk1M8 hZUrtChh9a0vKK4v/pN2fmE= =bn/f -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
