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

Re: Subversion 1.2 this year?

From: <kfogel_at_collab.net>
Date: 2004-11-03 16:37:45 CET

"Peter N. Lundblad" <peter@famlundblad.se> writes:
> Would this mean moving new features to 1.3 and releasing 1.2 when the real
> bugs in that milestone are fixed, or do you just want those bugs cleaned
> before starting on locking?

I think we should try to keep locking in 1.2, but expect the feature
to gel closer to the end of the milestone.

We can revisit this judgement when all the 1.2 bugs are fixed, of
course. If locking is still far from completion at that point, we may
decide to release 1.2 right away, then release 1.3 when locking is
ready (and not delay 1.3 on bug fixes too much, just make it the
locking release).

> There are some bugs that require new API:s (i.e. 2064 and possibly
> others). Don't you think there are other bugs that could also be fixed in
> an 1.1.x release?

Well, look at it this way: anything that's fixed for 1.1.x is also
fixed for 1.2, by definition.

In other words, if a change is to be fixed in 1.2, the question of
whether to nominate that change for a 1.1.x release is entirely
separate. It may or may not get into 1.1.x, but it *definitely* goes
into 1.2.

I see you've started #2064, by the way -- that's great! I'll race you
(with 2106) :-).


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 3 18:32:14 2004

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.