On 8/24/05, David Jencks <[EMAIL PROTECTED]> wrote:
> > Can we agree on the features first and pick the date based on
> > that?
>
> I would like to pick an absolute minimum feature set and push really
> hard for the date.
I'm in favor of this as well. But we need to get people assigned to
issues *before* we decide on a date for the release.
> >> 3) I would like to see the M5 cut with a 5 day window between QA code
> >> freeze and release. Thus QA cut on 9/4. Does this sound reasonable?
> >
> > It took substantially more than 5 days to complete TCK testing for
> > M4, plus we have to do it all for Tomcat this time too. Granted that
> > was
> > the week of OSCon, but I'm not altogether sure that 5 days is enough.
I think that five days is enough, especially if we only include issues
that are:
a) Assigned to someone
b) Able to be completed by the release date
> Basically, i'm willing to drop just about any jira entry I haven't
> signed up for and doesn't really break stuff. If no one will sign up
> and fix some of these promptly, what else should we do?
I agree, if we can't get someone to which to assign an issue, then it
should not be included unless there's damn good reason.
At this time, I've only got one issue assigned to me and it will be
completed in time for inclusion in M5.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
The Castor Project
http://www.castor.org/
Apache Geronimo
http://geronimo.apache.org/
