Thanks, but I added it the Creating and Signing a Release page last night.
*
http://cwiki.apache.org/confluence/x/B2c#CreatingandSigningaDistribution-FastTrackinganImportantSecurityRelease
On 8/9/07, Paul Benedict <[EMAIL PROTECTED]> wrote:
> I'll volunteer to add this unless someone else wants
I'll volunteer to add this unless someone else wants to.
On 8/7/07, Martin Cooper <[EMAIL PROTECTED]> wrote:
>
> Have we codified this somewhere? I didn't see a commit go by, but then I'm
> still catching up.
>
> --
> Martin Cooper
>
>
> On 8/4/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> >
>
Have we codified this somewhere? I didn't see a commit go by, but then I'm
still catching up.
--
Martin Cooper
On 8/4/07, Niall Pemberton <[EMAIL PROTECTED]> wrote:
>
> Discovering that there is a way to avoid having to wait 24hrs for the
> mirrors to sync for security releases is a great find -
Discovering that there is a way to avoid having to wait 24hrs for the
mirrors to sync for security releases is a great find - good job Ted.
I'm happy with this proposed fasttrack process now.
Niall
On 8/3/07, Ted Husted <[EMAIL PROTECTED]> wrote:
> I checked with infrastructure as to the appropr
I checked with infrastructure as to the appropriate use of the
timestamp parameter in the mirroring link. Accordingly, I would
suggest the following template language to initiate a "fast-track"
vote for a #.#.#.x security-fix distribution. Now that we have a
procedure, the intent to fast-track a vo
On 8/3/07, Henri Yandell <[EMAIL PROTECTED]> wrote:
> In this case, it's not a new bug that had just shown up. It was
> kicking around the issue tracker for a fair while. I'd much rather see
> a normal vote happening, and am happy with a vote on private@ if it's
> for a security release and the iss
On 8/2/07, Ted Husted <[EMAIL PROTECTED]> wrote:
> So to sum up the post-mortem,
>
> Security Releases
>
> * When a serious security issue arises, we should try to create a
> #.#.#.1 branch on the last GA release, and apply to that branch only
> the security patch.
+1. Surgical.
> * If the pa
On 8/2/07, Ted Husted <[EMAIL PROTECTED]> wrote:
> So to sum up the post-mortem,
>
> Security Releases
>
> * When a serious security issue arises, we should try to create a
> #.#.#.1 branch on the last GA release, and apply to that branch only
> the security patch.
>
> * If the patch first appl
So to sum up the post-mortem,
Security Releases
* When a serious security issue arises, we should try to create a
#.#.#.1 branch on the last GA release, and apply to that branch only
the security patch.
* If the patch first applies to WebWork, or some other dependency,
beg the other group t
