[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: 0.32, the "1.0" milestone, and the 1.0 release.

From: Barry Scott <barry_at_barrys-emacs.org>
Date: 2003-10-04 12:46:55 CEST

I'm just checked to see what the state of Python API was in the issues.
There is one issue 1451. Is it still you're intention to ship 1.0
without a scripting API that works? In my world this is a gating
factor for adoption of subversion. I'm not trying to change your
mind on release criteria, I just want to know when this will be
important enough to make work. Then I can plan what I do accordingly.

I'll keep working with Russell to get svn.client working to help
get this usable. But I fear that at some point we will run out of
knowledge of how subversion and its bindings are supposed to work and
will need help from a core developer.


At 03-10-2003 05:50, kfogel@collab.net wrote:
>A lot of folks have been asking, "What's up with the issues marked for
>the '1.0' milestone? Are they after Beta, or before Beta, or what?"
>Okay, actually no one's been asking that. But I wanted start with a
>leading question, so I could pretend to answer it...
>The "1.0" milestone has been a dumping ground for issues that are
>nice-to-haves for a 1.0 release, but not truly required. I won't talk
>about particular issues here; anyone looking over the 25 or so "1.0"
>bugs can come to their own conclusions about which ones are important
>to fix before 1.0 and which aren't. And probably not come to exactly
>the same conclusion as someone else would, either :-).
>Over the next day, you'll see me moving many of them to a new "1.1"
>milestone, our first gradation in the hitherto-monolithic "Post-1.0"
>category. The rest will get moved to 0.32 or into the general
>Post-1.0 pool. None will be left in 1.0, because the only purpose of
>that milestone was as a holding area until we got to this point.
>I hope people are generally okay with this. I certainly don't expect
>everyone to agree with every decision, but do ask that you wait until
>you have an overview of all the shifts before objecting to a
>particular assignation. Some serious triage is necessary, or we'll be
>here all day, know what I mean? :-)
>As for 0.32, Beta, and 1.0: The plan is that once 0.32 is complete, we
>are officially "in Beta". At that point, we will make a release
>branch (called "stabilize-1.0" or something), which will be for
>bugfixes only. There will be cross-pollination between trunk and the
>1.0 stabilization branch, but risky new features will stay confined to
>trunk. When the branch is ready, we release 1.0, and have a party.
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 4 12:48:39 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.