Re: Time for httpd 2.6.x?

On Mon, Nov 04, 2019 at 09:35:09PM +0100, Ruediger Pluem wrote: > On 10/25/2019 12:52 PM, Yann Ylavic wrote: > > My feeling is that it's easier to start from trunk, no strong feeling > > (an intuitive one). > > > > So how about: > > 0. github workflow? meanwhile... > > 1. compare trunk/2.4.x

Re: Time for httpd 2.6.x?

On 10/25/2019 12:52 PM, Yann Ylavic wrote: > On Wed, Oct 23, 2019 at 11:06 AM Stefan Eissing > wrote: >> >> As I said in the past, my idea would be to: >> - trunk -> trunk-old, >> - copy 2.4.x -> trunk >> - any feature to bring from trunk-old to the new trunk needs a champion, >> e.g. someone

Re: Time for httpd 2.6.x?

Il giorno dom 3 nov 2019 alle ore 18:52 Jim Jagielski ha scritto: > > > > On Nov 1, 2019, at 11:59 AM, Luca Toscano wrote: > > Il giorno mar 29 ott 2019 alle ore 18:31 Graham Leggett > ha scritto: > > > On 29 Oct 2019, at 15:51, Jim Jagielski wrote: > > My only question regards workflow w/

Re: Time for httpd 2.6.x?

> On Nov 1, 2019, at 11:59 AM, Luca Toscano wrote: > > Il giorno mar 29 ott 2019 alle ore 18:31 Graham Leggett > mailto:minf...@sharp.fm>> ha scritto: >> >> On 29 Oct 2019, at 15:51, Jim Jagielski wrote: >> >>> My only question regards workflow w/ trunk. Right now, I think we all agree >>>

Re: Time for httpd 2.6.x?

Il giorno mar 29 ott 2019 alle ore 18:31 Graham Leggett ha scritto: > > On 29 Oct 2019, at 15:51, Jim Jagielski wrote: > > > My only question regards workflow w/ trunk. Right now, I think we all agree > > that there are codepaths and features in trunk that are not as stable as we > > would

Re: Time for httpd 2.6.x?

On 29 Oct 2019, at 15:51, Jim Jagielski wrote: > My only question regards workflow w/ trunk. Right now, I think we all agree > that there are codepaths and features in trunk that are not as stable as we > would like. Which is fine... trunk is CTR. But we do need some way to vet > those

Re: Time for httpd 2.6.x?

> On Oct 29, 2019, at 9:36 AM, Eric Covener wrote: > > On Tue, Oct 29, 2019 at 9:18 AM Luca Toscano > wrote: >> >> Hi everybody, >> >> Il giorno ven 25 ott 2019 alle ore 12:52 Yann Ylavic >> ha scritto: >>> >>> So how about: >>> 0. github workflow?

Re: Time for httpd 2.6.x?

On Tue, Oct 29, 2019 at 9:18 AM Luca Toscano wrote: > > Hi everybody, > > Il giorno ven 25 ott 2019 alle ore 12:52 Yann Ylavic > ha scritto: > > > > So how about: > > 0. github workflow? meanwhile... > > 1. compare trunk/2.4.x (inventory) > > 2. discuss unused/deprecated in trunk to cleanup >

Re: Time for httpd 2.6.x?

Hi everybody, Il giorno ven 25 ott 2019 alle ore 12:52 Yann Ylavic ha scritto: > > So how about: > 0. github workflow? meanwhile... > 1. compare trunk/2.4.x (inventory) > 2. discuss unused/deprecated in trunk to cleanup > 3. address STALLED entries in trunk if it's not for compatibily

Re: Time for httpd 2.6.x?

On Fri, Oct 25, 2019 at 1:58 PM Jim Jagielski wrote: > > I'm fine w/ whatever we all decide. +1

Re: Time for httpd 2.6.x?

> On Oct 25, 2019, at 6:59 AM, Graham Leggett wrote: > > On 24 Oct 2019, at 14:14, Jim Jagielski wrote: > >> Going from 2.4.x to 2.6.x implies an ABI break... Up to now, all backports >> from trunk have maintained the 2.4.x ABI backwards compatibility. >> >> So I would propose that if we

Re: Time for httpd 2.6.x?

On 24 Oct 2019, at 14:14, Jim Jagielski wrote: > Going from 2.4.x to 2.6.x implies an ABI break... Up to now, all backports > from trunk have maintained the 2.4.x ABI backwards compatibility. > > So I would propose that if we do the below, which I am fine w/ BTW, that the > 1st issues we

Re: Time for httpd 2.6.x?

On Wed, Oct 23, 2019 at 11:06 AM Stefan Eissing wrote: > > As I said in the past, my idea would be to: > - trunk -> trunk-old, > - copy 2.4.x -> trunk > - any feature to bring from trunk-old to the new trunk needs a champion, e.g. > someone who does the work (porting and test cases) I'm not

Re: Time for httpd 2.6.x?

Going from 2.4.x to 2.6.x implies an ABI break... Up to now, all backports from trunk have maintained the 2.4.x ABI backwards compatibility. So I would propose that if we do the below, which I am fine w/ BTW, that the 1st issues we tackle after branching 2.6.x from httpd-24 are all the ABI

Re: Time for httpd 2.6.x?

Disclaimer: I've been pretty much absentee for a while so take my opinions with a grain of salt. >From a PR perspective, 7 years is a heck of a long time and it would be great to remind people that httpd is in fact an actively developed project doing exciting and modern things. mod_md all by

Re: Time for httpd 2.6.x?

Thanks a lot for all the answers, waiting for more people to chime in! What I personally like (at a very high level): 1) create a 2.6.x branch from 2.4.x and start backporting commits from trunk (with votes etc..), up to the point that we feel 2.6.0 GA is ready, then follow the regular release

Re: Time for httpd 2.6.x?

Hi All, I agree with CJ here. As I said in the past, my idea would be to: - trunk -> trunk-old, - copy 2.4.x -> trunk - any feature to bring from trunk-old to the new trunk needs a champion, e.g. someone who does the work (porting and test cases) To some, that looks like we do not honour

Re: Time for httpd 2.6.x?

Hi Luco, I've nothing against a 2.6.x branch. My only fear is things in trunk that is incomplete and or not enough reviewed. In other words, our backport mechanism with at least 3 votes is safeguard for me. My personal point of view is that 2.6.x should be built with backports from trunk,

Re: Time for httpd 2.6.x?

I guess you would want to take trunk as a starting point? We would probably start with releasing (more) 2.5 alphas/betas. Maybe we can defer branching to the point, where we aim at the first 2.6.0 GA. At least I am not aware of a pressing need to do more breaking changes in trunk right now

Re: Time for httpd 2.6.x?

+1 Luca Toscano schrieb am Mi., 23. Okt. 2019, 08:29: > Not even a comment? :) > > Luca > > Il giorno dom 13 ott 2019 alle ore 20:58 Luca Toscano > ha scritto: > > > > Hi everybody, > > > > in trunk's STATUS there are a lot of suggestions about things to > > improve/change for 2.6.x. There

Re: Time for httpd 2.6.x?

Not even a comment? :) Luca Il giorno dom 13 ott 2019 alle ore 20:58 Luca Toscano ha scritto: > > Hi everybody, > > in trunk's STATUS there are a lot of suggestions about things to > improve/change for 2.6.x. There have been discussions during the past > couple of years about how/when/if to

Time for httpd 2.6.x?

Hi everybody, in trunk's STATUS there are a lot of suggestions about things to improve/change for 2.6.x. There have been discussions during the past couple of years about how/when/if to create a 2.6 release branch, but for a lot of reasons we didn't do any progress. Would it be something to