[POLL] Onwards to 1.3.0? Or 2.0.0?

["William A. Rowe, Jr." <wr...@rowe-clan.net>]

Folks,

based on Justin's and others' comments, I'd like to start a poll of where
we stand.  1.2.x has evolved nicely into a quite stable platform.  We have
several new code bases proposed for inclusion in the 'next' version.  There
is also some desire to bring things to closure, drop deprecated interfaces,
rename badly named interfaces, and possibly refactor where specific elements
live within the apr-* family.

So with a goal of a release sometime in the next few months, we've come to
the fork in the road.  Individually, would we rather see...

 [ ]  1.3.0 released, all new features added
 [ ]  2.0.0 released, new + deprecation + renames + reorganizations

We'll call the poll results on Sunday to decide where trunk moves next.

Note that if there is a strong desire for 1.3.0, we are reaching the point
where we need to do parallel work to move twords 2.0.0 regardless, which
would mean a 1.3.0 branch at this point.  The question in front of us is,
do we really want to add another branch to maintain, or simply improve on
1.2.x until 2.0.0 is ready?

Re: [POLL] Onwards to 1.3.0? Or 2.0.0?

[Bojan Smojver <bo...@rexursive.com>]

On Wed, 2007-01-03 at 12:46 -0600, William A. Rowe, Jr. wrote:

> So with a goal of a release sometime in the next few months, we've come to
> the fork in the road.  Individually, would we rather see...
> 
>  [X]  1.3.0 released, all new features added
>  [X]  2.0.0 released, new + deprecation + renames + reorganizations

Rationale:

We should give new functionality to current 1.x users, without the need
to redo their source/binary code. Given that 1.3 is backward compatible
with 1.2, it is 1.3 that should be maintained into the future. At the
same time, people willing/able to change should be able to pick the lot
up using new API/ABI in 2.0.

-- 
Bojan

Re: [POLL] Onwards to 1.3.0? Or 2.0.0?

["William A. Rowe, Jr." <wr...@rowe-clan.net>]

William A. Rowe, Jr. wrote:
> 
> So with a goal of a release sometime in the next few months, we've come to
> the fork in the road.  Individually, would we rather see...
> 
>  [ ]  1.3.0 released, all new features added
>  [X]  2.0.0 released, new + deprecation + renames + reorganizations

Although I see some small value in 1.3.0, if we are adding features this
really seems like the right fork to move those users looking -for the new
features- towards the next iteration of the API.

My 2c