[wp-hackers] WordPress 3.0.3

[Mitch Canter]

People are hesitant to update - especially if they have large sites with lots of plugins.  Or they've updated back when it wasn't so easy and had a bad experience.  For some reason people are just hesitant to respond to that notice I've seen.

Mitch

> From: hempsworth at gmail.com
> Date: Wed, 8 Dec 2010 20:39:07 +0000
> To: wp-hackers at lists.automattic.com
> Subject: Re: [wp-hackers] WordPress 3.0.3
> 
> Although I agree a published explanation of the importance is a great
> idea; with our 1-click upgrade built into core I'm surprised there's
> an issue.
> 
> I don't imagine many users have a problem installing software updates
> on their computers... Or maybe they do!?
> 
> -- Alex
> 
> Sent from my iPhone
> 
> On 8 Dec 2010, at 20:35, Blue Chives <info at bluechives.com> 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