Hi, Jacob;
  The odd-numbered releases are the dev/unstable releases (aka: trunk). This 
will make the next release 2.6... potentially, 3.0 if we think there have been 
enough changes. I personally don't think there have been, but that's ultimately 
a decision we'll make as a community.

   When 2.5 is API/ABI solidified, trunk gets branched (svn copy) to 2.6 to 
live on as a stable branch. Then, trunk gets a bump up to 2.7.
-- 
Daniel Ruggeri


-------- Original Message --------
From: Jacob Perkins <jacob.perk...@cpanel.net>
Sent: November 2, 2017 11:39:59 AM CDT
To: dev@httpd.apache.org
Subject: Re: [NOTICE] Intent to T&R 2.5.0-alpha

Howdy,

Could you clear up some confusion for me? 

We have
2.2 and 2.4.

Is 2.5 the ‘dev’ branch of 2.6? Or are we going 2.2 => 2.4 => 2.5?

—
Jacob Perkins
Product Owner
cPanel Inc.

jacob.perk...@cpanel.net <mailto:jacob.perk...@cpanel.net>
Office:  713-529-0800 x 4046
Cell:  713-560-8655

> On Nov 2, 2017, at 3:41 AM, Daniel Ruggeri <drugg...@primary.net> wrote:
> 
> Hi, all;
> 
>    As has been chatted about in other threads, I hope to T&R 2.5.0-alpha
> in the coming days. I suppose notice is too soon to do so this evening,
> so I'll plan for early next week.
> 
>    Also, as a side note, part of my motivation to be more involved as RM
> is to help establish a more regular release cadence. I envision a world
> where much of the drudgery of our RM processes are automated and have
> begin putting together some scripts to help with that goal. Nothing
> beats practice, though, to identify *all* the places that have to be
> automated so hopefully after this alpha is out the door we'll be in a
> good spot with some scripts and as minimal-as-possible manual procedures.
> 
> -- 
> Daniel Ruggeri
> 

Reply via email to