You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Eric Covener <co...@gmail.com> on 2021/09/02 13:06:05 UTC

Re: release?

Since you are going through this I wanted to mention:

I think the public doc we have should mention everything that's done
during ther release, even the security stuff that is somewhat private.
The ASF-wide security policy is already public
(https://www.apache.org/security/committers.html) and this is just the
mechanics of it for us.

Anyone object?  This way we have one linear place to point to.

On Mon, Aug 30, 2021 at 7:36 AM stefan@eissing.org <st...@eissing.org> wrote:
>
> In what state is our release handling? Given someone holding my hand, could I do it? Or is it better to look someone over the shoulder while he does it?
>
> Cheers,
> Stefan



-- 
Eric Covener
covener@gmail.com

Re: release?

Posted by "stefan@eissing.org" <st...@eissing.org>.
The v2 release scripts in ^/httpd/dev-tools do now work for me
to create the tarballs, checksums and signatures for a release
vote and push them to dist.apache.org.

The steps after a vote need some more work. I will do that in the
coming days. However, since we can do a vote now, this is not that
pressing.

The "announce.sh" part should stay usable as it is. I have no plans 
to update that one, since I have 0 experience what this really does 
and where any problems/room for improvements are.

Cheers,
Stefan


> Am 02.09.2021 um 16:53 schrieb Ruediger Pluem <rp...@apache.org>:
> 
> 
> 
> On 9/2/21 3:06 PM, Eric Covener wrote:
>> Since you are going through this I wanted to mention:
>> 
>> I think the public doc we have should mention everything that's done
>> during ther release, even the security stuff that is somewhat private.
>> The ASF-wide security policy is already public
>> (https://www.apache.org/security/committers.html) and this is just the
>> mechanics of it for us.
>> 
>> Anyone object?  This way we have one linear place to point to.
> 
> +1 Looks sensible. The details of an actual security issue should not be public until we make it so, but the procedure we use can be.
> 
> Regards
> 
> RĂ¼diger
> 


Re: release?

Posted by Ruediger Pluem <rp...@apache.org>.

On 9/2/21 3:06 PM, Eric Covener wrote:
> Since you are going through this I wanted to mention:
> 
> I think the public doc we have should mention everything that's done
> during ther release, even the security stuff that is somewhat private.
> The ASF-wide security policy is already public
> (https://www.apache.org/security/committers.html) and this is just the
> mechanics of it for us.
> 
> Anyone object?  This way we have one linear place to point to.

+1 Looks sensible. The details of an actual security issue should not be public until we make it so, but the procedure we use can be.

Regards

RĂ¼diger