Perhaps one of the committers could fix MYFACES-359 for me before 1.0.10
closes? It's a very simple fix (patch included), and is a spec-related
issue.

Thanks in advance,
h.

> -----Original Message-----
> From: Sean Schofield [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, July 27, 2005 7:21 AM
> To: MyFaces Development
> Subject: Re: MyFaces 1.0.9: how old? how stable? what's next?
> 
> I agree we have fixed a bunch of bugs lately and that is encouraging.
> I'm just saying that we should make one last push today and tomorrow
> to close a few more if we can.  I will put up the RC late Thursday if
> everyone is agreeable.
> 
> sean
> 
> 
> On 7/27/05, Martin Marinschek <[EMAIL PROTECTED]> wrote:
> > thing is that issues keep flowing in for the MyFaces 1.0.9 release,
we will
> > not be knowing if this has been fixed in any of the new builds if we
don't
> > give out a new release.
> >
> >  and: even though a 100 bugs remain open (80 with the last release)
we have
> > fixed approximately 50-100 since the last release, if I am right
with my
> > numbers.
> >
> >  So I would definitely go for a new release!
> >
> >  regards,
> >
> >  Martin
> >
> >
> > On 7/27/05, Sean Schofield <[EMAIL PROTECTED]> wrote:
> > > I think we should hold off on the next release but I see I am out
> > numbered.  ;-)
> > >
> > > Why don't I put up a RC using the bootstrap procedure?  I will try
and
> > > get one up in the next few days.
> > >
> > > A few points:
> > >
> > > 1.) We might want to consider 1.0.10 instead of 1.1.0 and save the
1.1
> > > designation for when we are officially JSF compliant.
> > >
> > > 2.) We should not start voting on the RC until we have at least a
RC3.
> > > Last time we started voting on RC1, RC2, etc. after a few days and
> > > there were still tons of bug reports coming in.
> > >
> > > 3.) We should fix as many of the outstanding JIRA issues as we can
in
> > > the next few days.  There are 100+ JIRA issues.  IMO that is too
many
> > > outstanding issues before a release.
> > >
> > > 4.) Noncommitters should vote (in JIRA) for the outstanding issues
> > > they want fixed the most.  That will help us to prioritize them.
> > >
> > > 5.) New issues to be fixed before the release should be added to
JIRA.
> > > Don't report them on the dev list (we had some of this last go
> > > round.)
> > >
> > > sean
> > >
> >
> >
> 


Reply via email to