On Wed, Mar 12, 2008 at 11:36 AM, David Glasser
<glasser_at_davidglasser.net> wrote:
> > I think 'beta' is the way to go. I know Mark Phippard will kill me :-),
> > but a beta is likely to attract a lot of attention, and on a release
> > this big, it's worth having one before we go into the (implied)
> > stability of an RC.
>
> Agreed. A release candidate should be a release candidate: it should
> be something that has all the ingredients for a release, and just
> needs to be shaken out a little. We're not quite there yet.
I will just save time and reply to both of you.
I am just asking you both (really everyone) to think of this a little
more objectively. Why are we not ready yet? Why does this not have
the stability we need? If we are not ready, it ought to be more than
a feeling. What is the list of things that has to be done in order to
be ready. I think we are just wasting time thinking some bug report
might arrive that will have made this idling worth it. We have never
issued an RC1 before that did not have some bugs. IMO, the current
code has all the qualities of an RC. I am not ashamed at all of the
code as it exists today, and I do think it is of release quality.
People are free to disagree with me, but I would just like our policy
to be driven by something other than a gut feeling or fear of a bug.
If we are not ready for RC than I for one want to see a list of what
we have to get done so that we are ready. I do not think that is a
lot to ask. cmpilato, pburba, julian and myself will all be in
California next week. If there are some things to do I'd like to know
so we can talk about who can look into them and help keep things
moving.
By every time-based standard we have set for ourselves in the past, we
would have either already released an RC by now, or would at least be
putting the absolute finishing touches on it. I think we are ready
(the two known issues I mentioned not-withstanding).
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-03-12 16:49:15 CET