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

upcoming issues sweep

From: <kfogel_at_collab.net>
Date: 2003-05-07 21:39:42 CEST

Just a bit of warning, folks:

Greg Stein and Jack Repenning are visiting Chicago this week, which
means we have them in a room with Mike Pilato, Ben Collins-Sussman,
and myself. So we're taking this opportunity to do a sweep over all
the pre-1.0 issues and consider each one afresh: Has X been resolved?
Has the situation changed in some important way? Does the issue still
need to be pre-1.0?

Happily, in a lot of cases, the issue can be moved to Post-1.0, and we
are moving them possible. The motivation for this is twofold:

   1) At some point, when we get closer to 1.0, we'll make a release
      branch, to minimize the impact of release discipline on
      non-release-related work. But we want the amount of time we
      spend in this state to be as little as possible, since it's
      always painful to be keeping two lines in sync... (And we want
      to *get* to that stage as soon as possible too :-) ).

   2) The sooner we get 1.0 out, the sooner everyone can join in on
      the sexy stuff (like, ahem, better history tracking). Believe
      me, the people concentrating on 1.0 bugfixes right now would
      love to be participating more in the sexy stuff -- and the
      project as a whole benefits when we have more minds devoted to
      these hard problems.

So all of these reasons point to releasing 1.0 as soon as we can,
though not sacrificing any important quality points, of course.
Hence, the issue churn you'll be seeing soon.

And if you see anything that strikes you as a truly bad call, please
post to the list right away, as always.

-Karl et al

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed May 7 22:21:28 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.