1.5.0: Moving forward

["Hyrum K. Wright" <hy...@mail.utexas.edu>]

We did it.  We shipped 1.5.

In some ways, it feels a lot like releasing 1.0.  We've worked really
hard to make sure that we've got a quality product out the door, but at
the same time, there is still a lot left to be done.  (A casual glance
at STATUS will verify that.)  To me, we've got two areas to focus on:
1.5.x patch releases and 1.6.

I'd like to plan on releasing 1.5.1 within the next 4 to 6 weeks.  We've
already got a number of items queued in STATUS, and I expect that there
are more yet to be fixed.  This time frame would mean releasing by the 
end of July.  Does this sound feasible?

As for 1.6, it looks like we already have several new features on trunk,
with several others either planned or on branches.  This includes (but 
certainly isn't limit to):
  * better caching support
  * augmented diff representation
  * Gnome and KDE password integration
  * Summer of Code projects

Given this activity, think we could realistically shoot for a 1.6
release by the end of 2008.  That's just a ballpark number, of course,
but I think quicker minor releases, justified by significant features,
will make both our users and developers happy -- and make the release
process much more manageable.

So whether you are a developer, user, or both, go out on the town,
celebrate with your significant other, or just take a break for a few
days; you deserve it.  When you come back, there will be bug reports a
plenty, and great new features to implement.  Thanks again.

-Hyrum

Re: 1.5.0: Moving forward

[Lieven Govaerts <sv...@mobsol.be>]

Hyrum K. Wright wrote:
> We did it.  We shipped 1.5.
>
> In some ways, it feels a lot like releasing 1.0.  We've worked really
> hard to make sure that we've got a quality product out the door, but at
> the same time, there is still a lot left to be done.  (A casual glance
> at STATUS will verify that.)  To me, we've got two areas to focus on:
> 1.5.x patch releases and 1.6.
>
> I'd like to plan on releasing 1.5.1 within the next 4 to 6 weeks.  We've
> already got a number of items queued in STATUS, and I expect that there
> are more yet to be fixed.  This time frame would mean releasing by the 
> end of July.  Does this sound feasible?
I don't know how keen people are for doing all the test work in the 
middle of the holiday period, but with the amount of changes in 1.5 it's 
reasonable to expect issues showing up in the coming weeks that we'll 
want to fix asap. So end of July looks like a good plan to me.
> As for 1.6, it looks like we already have several new features on trunk,
> with several others either planned or on branches.  This includes (but 
> certainly isn't limit to):
>  * better caching support
>  * augmented diff representation
>  * Gnome and KDE password integration
>  * Summer of Code projects
There's only one GSoC project active anymore, the authz improvements 
project won't start.

I personally plan to work on two things:
1. getting ra_serf ready for prime time. This requires fixing the 
existing bugs, keeping up to date with 1.6 development and fixing the 
functional gaps with ra_neon (mostly authn/authz related).
2. finishing the functional and technical spec of 'svn obliterate'.

Given the limited amount of time I can spend on Subversion development 
every evening that's ambitious, but I'd like to try :-)

Lieven




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org