On Mon, Apr 04, 2011 at 08:21:56AM -0700, Todd Gleason wrote:
> > -----Original Message-----
> > From: Andy Levy [mailto:andy.levy_at_gmail.com]
> > Sent: Monday, April 04, 2011 7:37 AM
> > To: Schroeder, Hartmut
> > Cc: users_at_subversion.apache.org
> > Subject: Re: release date of Subversion 1.7
> > On Mon, Apr 4, 2011 at 09:34, Schroeder, Hartmut
> > <Hartmut.Schroeder_at_plath.de> wrote:
> > > I know that, but we would appreciate a release date we could belief
> > on.
> > When it's ready.
> I expected much the same answer when I saw this question. I'd like to ask some more easily answerable questions though.
> Is the release status at
> current? I have checked this on occasion and not noticed any obvious
> changes for a long time.
It could need some updates, but still provides a good high level idea
of where things stand.
Some of the problems that have and are being worked on are not even listed
on that page. E.g. we're still fixing wc-ng performance issues but progress
on that is mostly tracked on the dev@ list. Basically, as long as the wc-ng
item stays yellow there are performance or other regressions from 1.6.x
so we cannot release.
The list of issues with 1.7 and 1.7.x milestones is also quite relevant.
They are linked from the "Issue triage" item.
> I noticed that, at the top of that page, it still says "Q1 2011" for
> release. Also, what about the branch? Has the "Branch 1.7.x" been
> created yet?
A 1.7.x branch has not been created.
> I definitely understand about software slipping. Even so, those of us
> anxiously waiting for the next release would much appreciate knowing
> what the current status is.
There is no reason to get excited right now.
At some point the beta testing phase will start.
Then there's a reason to get excited :)
1.6.x is very stable now, with some interesting additional fixes proposed
for 1.6.17: https://svn.apache.org/repos/asf/subversion/branches/1.6.x/STATUS
It's unlikely that 1.7.0 will initialy be as stable as 1.6.x.
So I would recommend staying with 1.6.x for up to 6 months even after 1.7.0
is released. Unless you really need one of the new 1.7.x features right away.
Received on 2011-04-04 17:42:57 CEST