[wp-hackers] WordPress 3.0.3

[Mitch Canter]

Sorry, maybe I mis-spoke as to what I meant.

I know that there's release posts and changesets, but I mean more of a "security release lifecycle".

Etc: Someone finds a bug, it gets reported to trac, some things happen, then a security release is done.

I'd like to fill in the blanks as to what happens from start to finish and get a complete look at "this is what happens when we find a bug that is urgent enough to get a security release".

Make sense?

Mitch

> From: paul at codehooligans.com
> Date: Wed, 8 Dec 2010 15:36:44 -0500
> To: wp-hackers at lists.automattic.com
> Subject: Re: [wp-hackers] WordPress 3.0.3
> 
> http://codex.wordpress.org/Version_3.0.3
> http://core.trac.wordpress.org/changeset/16803
> 
> On Dec 8, 2010, at 3:33 PM, Blue Chives wrote:
> 
> > An explanation would be a great idea,  especially to help us when dealing with recent converts.
> > 
> > Cheers
> > 
> > John. 
> > 
> > On 8 Dec 2010, at 20:31, Mitch Canter <mitch at mitchcanter.com> wrote:
> > 
> >> 
> >> On a bit of a related subject, I have a question.  Is there an online resource with the step-by-step of (or could someone enlighten the process of) how a Security Release rolls out from start to finish? There are a lot of users that are questioning the need for 2 releases in such a short time and having a detailed explanation (I think) would serve as a fantastic resource as to the why (and not just to "here's a new release go download it" which may offput some users).
> >> 
> >> Mitch C
> >> 
> >>> From: wp at andrewnacin.com
> >>> Date: Wed, 8 Dec 2010 14:21:55 -0500
> >>> To: wp-hackers at lists.automattic.com
> >>> Subject: Re: [wp-hackers] WordPress 3.0.3
> >>> 
> >>> On Wed, Dec 8, 2010 at 2:16 PM, Milan Dinić <liste at srpski.biz> wrote:
> >>> 
> >>>>> 
> >>>>> I'd advise you to update your plugin compatibility as appropriate.
> >>>> Plugins
> >>>>> should be unaffected by this release.
> >>>> 
> >>>> 
> >>>> I see that now when your mark plugin as compatible with one version, all
> >>>> versions from that branch will be reported as compatible.
> >>>> 
> >>>> For example, plugins that are marked as compatible with 3.0, 3.0.1 and
> >>>> 3.0.2
> >>>> are now marked as compatible up to 3.0.3.
> >>> 
> >>> 
> >>> This isn't always going to be the case, but I do agree there is room for
> >>> improvement here.
> >>> 
> >>> We're going to work on a way to cause the plugin compatibility system to
> >>> treat certain releases (those we manually specify) as equal.
> >>> 
> >>> Nacin
> >>> _______________________________________________
> >>> wp-hackers mailing list
> >>> wp-hackers at lists.automattic.com
> >>> http://lists.automattic.com/mailman/listinfo/wp-hackers
> >> 
> >> _______________________________________________
> >> wp-hackers mailing list
> >> wp-hackers at lists.automattic.com
> >> http://lists.automattic.com/mailman/listinfo/wp-hackers
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> 
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers