git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 2.4.38


I’m all for this as well, because people want the new hotness. That said, for people downstream that have to support 
httpd, y’all are releasing really fast. I get it, and we haven’t really had any problems (minus a weird semaphore issue we
haven’t tracked down yet), I’m noticing an increase of releases lately.

Just curious what is the rush lately? Is this all a build up to 2.6 coming out or something else?



> On Nov 8, 2018, at 3:11 AM, Stefan Eissing <stefan.eissing@xxxxxxxxxxxxx> wrote:
> 
> 
>> Am 07.11.2018 um 16:15 schrieb Jim Jagielski <jim@xxxxxxxxxxx>:
>> 
>> Now that we have a 2.4.37 out, one in which the number of enhancements and fixes and feature were limited, it makes sense to consider having a 2.4.38 release somewhat "soonish", esp considering the number of backports that lack only a single vote.
>> 
>> Comments?
> 
> I am all for it. And I have reasons! :-)
> 
> 1. We are well on track to automate the whole thing nicely. We need some more iterations to make it tight. This is easier done in short intervals.
> 2. I think regular releases are good for the people here and motivate people from outside to contribute.
> 3. h2 and Let's Encrypt still get attention and there are some small improvements I'd like to throw out there. Nothing serious, just would be nice.
> 
> Cheers,
> 
> Stefan

Super off topic but this is one of the best communities I deal with in my day to day, even when
y’all are mad you’re good to each other, means a lot to those of us that just need to follow the feed.
Thank you all for that.

Thanks,
Cory McIntire
Release Manager - EasyApache 
cPanel, L.L.C.

Attachment: smime.p7s
Description: S/MIME cryptographic signature