Re: [VOTE]: Proposal for a Xerces-C2.6.0 release

[PeiYong Zhang]

James,

    Yes, we are evaluating the outstanding blockers and other blocker candidates and
hopefully we can reach the conclusion that if the proposed the release shall go ahead or ...


Rgds,
PeiYong

James Berry <[EMAIL PROTECTED]> wrote on 09/27/2004 12:57:26 PM:

> +0. (That would be a -1, but I don't think that would be quite fair
> since I don't have any time currently to devote to Xerces bug fixes!)
>
> I would certainly consider changing that to a +1, but I have the
> following issue:
>
> Since we typically have a fairly long cycle between releases, and don't
> tend to do bug-fix releases apart from the major releases, I want to
> make sure that we drive this release based on what needs to be
> achieved, rather than by a somewhat arbitrary calendar date.
>
> I note that in the bug database there are 7 issues listed as "blocker",
> 6 as "critical" and 25 as "major". Additionally there are 7 issues that
> have been "voted" for as popular to have fixed.
>
> Can we get any sort of consensus among committers on which bugs have to
> be fixed before the release? (these should be set to priority
> "blocker", I would think). In this way we can communicate criteria for
> a release other than a simple date.
>
> All that said, I also realize that in any software release there must
> be a certain amount of triage. A lot has been accomplished since 2.5,
> and many important bugs fixed. I'm not trying to hold up 2.6
> arbitrarily, but simply to make sure that we discussion about good
> criteria for a release.
>
> So:
>
>    - Are those blockers all really blockers?
>    - Are there others on the list that should be blockers?
>    - Will we "block" the release based on status of the blockers?
>
> -jdb
>
> On Sep 23, 2004, at 12:26 PM, PeiYong Zhang wrote:
>
> >
> > Hi all,
> >
> >    There are many bug fixes[1] to the XercesC2_5_0 and new features[2]
> > implemented since
> > the release of XercesC2_5_0, it is time to produce a new release,
> > XercesC2_6_0.
> >    
> >    I'll suggest that we should aim to publish this by the end of
> > September, and in the mean
> > time try and fix as many outstanding bugs as possible before the
> > closing time, EST 12:00 PM, Sept. 29.
> >
> > Here's my +1.
> >
> > Rgds,
> > PeiYong
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>