Re: [NOTICE] Next Release Roll Update (Was: Re: rolling a non security release around Jan 13.)

[Ruediger Pluem]

On 1/15/25 4:09 PM, Eric Covener wrote:
>> Anyone opposed if I set aside a T&R for Jan 20th? I'd prefer to do it early 
>> in the week.
> 
> No issue here.
> 

+1

Regards

Rüdiger

Re: [NOTICE] Next Release Roll Update (Was: Re: rolling a non security release around Jan 13.)

[Eric Covener]

> Anyone opposed if I set aside a T&R for Jan 20th? I'd prefer to do it early 
> in the week.

No issue here.

Re: [NOTICE] Next Release Roll Update (Was: Re: rolling a non security release around Jan 13.)

[Jim Jagielski]

> On Jan 15, 2025, at 8:06 AM, Stefan Eissing via dev  
> wrote:
> 
> 
> 
>> Am 15.01.2025 um 13:07 schrieb Jim Jagielski :
>> 
>> At present STATUS is clear of all voted-and-promoted back ports.
>> 
>> Are we ready to roll or should we give it a day or so?
> 
> Just updated mod_md to the latest. Now fine from me to go.
> 
> Cheers,
> Stefan
> 

Anyone opposed if I set aside a T&R for Jan 20th? I'd prefer to do it early in 
the week.

--
Jim
"I don't need a compass to tell me which way the wind shines."

Re: [NOTICE] Next Release Roll Update (Was: Re: rolling a non security release around Jan 13.)

[Stefan Eissing via dev]

> Am 15.01.2025 um 13:07 schrieb Jim Jagielski :
> 
> At present STATUS is clear of all voted-and-promoted back ports.
> 
> Are we ready to roll or should we give it a day or so?

Just updated mod_md to the latest. Now fine from me to go.

Cheers,
Stefan

> --
> Jim
> "I don't need a compass to tell me which way the wind shines."
> 
> 
> 

Re: [NOTICE] Next Release Roll Update (Was: Re: rolling a non security release around Jan 13.)

[Eric Covener]

On Wed, Jan 15, 2025 at 7:09 AM Jim Jagielski  wrote:
>
> At present STATUS is clear of all voted-and-promoted back ports.
>
> Are we ready to roll or should we give it a day or so?
> --
> Jim
> "I don't need a compass to tell me which way the wind shines."

Only other thing I saw on the radar was
https://bz.apache.org/bugzilla/show_bug.cgi?id=55475 /  r1538776
But it looks like it was just flagged in a resynch so maybe good to go.



--
Eric Covener
cove...@gmail.com

[NOTICE] Next Release Roll Update (Was: Re: rolling a non security release around Jan 13.)

[Jim Jagielski]

At present STATUS is clear of all voted-and-promoted back ports.

Are we ready to roll or should we give it a day or so?
--
Jim
"I don't need a compass to tell me which way the wind shines."

Re: rolling a non security release around Jan 13.

[Jim Jagielski]

> On Jan 7, 2025, at 9:30 AM, Eric Covener  wrote:
> 
> On Tue, Jan 7, 2025 at 9:16 AM Jim Jagielski  > wrote:
>> On Jan 6, 2025, at 3:28 PM, Eric Covener  wrote:
>> 
>> Hi all, I'd like to do a release to pick up the various regression fixes.
>> I will likely begin early the week of the 13th.
>> 
>> There are still a few straight-forward STATUS entries in need of a vote.
>> 
>> If anyone would like a crack at RM'ing when the stakes are a bit
>> lower, let me know and we can collaborate on it.
>> 
>> 
>> I wouldn't mind trying... it's been quite awhile however :-)
> 
> Works for me!
> 
> There is an updated README and several automated steps courtesy of
> @Stefan Eissing in
> https://svn.apache.org/repos/asf/httpd/dev-tools/release
> Mostly the same underlying steps as traditionally done, but some nice
> guardrails and new stuff for security handling.



Thanks!

I've committed the patches from STATUS. Again, let me know if I've missed some 
steps.

--
Jim
"I don't need a compass to tell me which way the wind shines."

Re: rolling a non security release around Jan 13.

[Eric Covener]

On Tue, Jan 7, 2025 at 9:16 AM Jim Jagielski  wrote:
> On Jan 6, 2025, at 3:28 PM, Eric Covener  wrote:
>
> Hi all, I'd like to do a release to pick up the various regression fixes.
> I will likely begin early the week of the 13th.
>
> There are still a few straight-forward STATUS entries in need of a vote.
>
> If anyone would like a crack at RM'ing when the stakes are a bit
> lower, let me know and we can collaborate on it.
>
>
> I wouldn't mind trying... it's been quite awhile however :-)

Works for me!

There is an updated README and several automated steps courtesy of
@Stefan Eissing in
https://svn.apache.org/repos/asf/httpd/dev-tools/release
Mostly the same underlying steps as traditionally done, but some nice
guardrails and new stuff for security handling.

Re: rolling a non security release around Jan 13.

[Jim Jagielski]

> On Jan 6, 2025, at 3:28 PM, Eric Covener  wrote:
> 
> Hi all, I'd like to do a release to pick up the various regression fixes.
> I will likely begin early the week of the 13th.
> 
> There are still a few straight-forward STATUS entries in need of a vote.
> 
> If anyone would like a crack at RM'ing when the stakes are a bit
> lower, let me know and we can collaborate on it.
> 

I wouldn't mind trying... it's been quite awhile however :-)

--
Jim
"I don't need a compass to tell me which way the wind shines."