[wp-testers] UNSUBSCRIBE

Fri Dec 3 16:00:07 UTC 2010

> Send wp-testers mailing list submissions to
> 	wp-testers at lists.automattic.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.automattic.com/mailman/listinfo/wp-testers
> or, via email, send a message with subject or body 'help' to
> 	wp-testers-request at lists.automattic.com
>
> You can reach the person managing the list at
> 	wp-testers-owner at lists.automattic.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of wp-testers digest..."
>
>
> Today's Topics:
>
>    1. Re: [wp-hackers] WordPress 3.0.2 (Otto)
>    2. lister (Ed Smith)
>    3. testers at list (Ed Smith)
>    4. (no subject) (T3charmy ...)
>    5. Re: [wp-hackers] WordPress 3.0.2 (Andrew Nacin)
>    6. Re: WordPress 3.0.2 (Michael Clark)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 2 Dec 2010 14:41:45 -0600
> From: Otto <otto at ottodestruct.com>
> Subject: Re: [wp-testers] [wp-hackers] WordPress 3.0.2
> To: wp-testers at lists.automattic.com
> Cc: wp-hackers at lists.automattic.com
> Message-ID:
> 	<AANLkTi=VSBy+2QE8mwC5m5au4vTM3JnZ-s9L2gpn8Zcn at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> For reference, the actual code changes from 3.0.1 to 3.0.2 can be found
> here:
> http://core.trac.wordpress.org/changeset?old_path=/tags/3.0.1&new_path=/tags/3.0.2
>
> -Otto
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 2 Dec 2010 13:30:40 -0800
> From: Ed Smith <resrav7 at gmail.com>
> Subject: [wp-testers] lister
> To: wp-testers at lists.automattic.com
> Message-ID:
> 	<AANLkTimxq=8gPXnEbeQmZdvX0axvN9cKPEQGKEoZNzOX at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 2 Dec 2010 13:38:23 -0800
> From: Ed Smith <resrav7 at gmail.com>
> Subject: [wp-testers] testers at list
> To: wp-testers at lists.automattic.com
> Message-ID:
> 	<AANLkTimaiFkZ+uHrvL0Nc-h4x==O2Rr2obbGo_ZGN=kD at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
>
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 2 Dec 2010 16:09:15 -0600
> From: "T3charmy ..." <t3charmy at gmail.com>
> Subject: [wp-testers] (no subject)
> To: wp-testers at lists.automattic.com
> Message-ID:
> 	<AANLkTinKoCeu1O0107BN+-T=7=QqY4=yzCePuX6-bxC6 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> HTC Evo Android 2.2
>
>
> ------------------------------
>
> Message: 5
> Date: Thu, 2 Dec 2010 18:12:26 -0500
> From: Andrew Nacin <wp at andrewnacin.com>
> Subject: Re: [wp-testers] [wp-hackers] WordPress 3.0.2
> To: wp-testers at lists.automattic.com, wp-hackers at lists.automattic.com
> Message-ID:
> 	<AANLkTimtwcVktGjM_bSP45VCOnWP5tm6tPLwg-COpSpz at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Thu, Dec 2, 2010 at 3:23 PM, Trent Martin <trentmar at gmail.com> wrote:
>
>> I totally agree on the urgency of a security update, except for this:
>>
>> 1. It isn't just a security update, it contains a number of other bug
>> fixes;
>> 11 core files were modified.
>>
>
> Of those 11 changes, 9 of them were merged to the branch previously and
> were
> in trunk for some time.
>
> While only one was enough to trigger 3.0.3, seven changes were security
> fixes or enhancements in some way.
>
> It fixed four other really annoying and moderately severe bugs that were
> already backported to the branch.
>
> It was a security update. But since we maintain the 3.0 branch for
> regressions, major bugs, and security enhancements (which we will until
> 3.2
> beta), then a few other things got shipped with it. We were very pleased
> with the quality of every change in the release, which were all thoroughly
> re-inspected and re-tested. We carefully evaluated every other ticket
> under
> 3.0.x consideration for potential inclusion as well.
>
> List of changes:
> http://core.trac.wordpress.org/changeset?old_path=/tags/3.0.1&new_path=/tags/3.0.2
>
> 2. They thanked the guy who reported it for responsible disclosure which
>> usually means he would give them time to fix it before making it public,
>> which he did.
>>
>
> Correct. We decided to release.
>
> 3. It certainly must have taken at least a day or two to fix, test,
> prepare,
>> and package an official release so there certainly was enough time to at
>> least give us a courtesy heads up that an update was imminent.
>>
>
> As Pete Mall said, it took four hours from the initial report to final
> release. Mark, Ryan and I worked nonstop over that time. We do good work
> :-)
>
> 4. This isn't the first time they have done a surprise release.
>>
>
> Indeed, even some members of the core team were busy all day and didn't
> hear
> about it either. :-)
>
>  I realize this update probably won't break anything, but we still have to
>> go
>> through a full test run anyway. I certainly do appreciate the work the
>> WordPress team is doing but I wanted to express my voice as plugin
>> developer.
>>
>
> I believe your opinion as a plugin developer should be weighed against
> tens
> of millions of WordPress blogs and users.
>
> So what I would like to know is what I should monitor to get the earliest
>> and most consistent notification of updates?
>>
>
> I should have sent this email to wp-hackers the day of launch, but I
> forgot.
> But by no means count on that. Follow the WordPress Blog, Trac, your
> dashboard, etc.
>
> Regards,
> Nacin
>
>
> ------------------------------
>
> Message: 6
> Date: Thu, 2 Dec 2010 22:39:28 -0500
> From: Michael Clark
> 	<031737d98884bcc7ae545aff35358b23.wp-testers at planetmike.com>
> Subject: Re: [wp-testers] WordPress 3.0.2
> To: wp-testers at lists.automattic.com
> Message-ID: <p06240800c91e1629be80@[192.168.1.102]>
> Content-Type: text/plain; charset="us-ascii" ; format="flowed"
>
> At 6:12 PM -0500 12/2/10, Andrew Nacin wrote:
>>On Thu, Dec 2, 2010 at 3:23 PM, Trent Martin <trentmar at gmail.com> wrote:
>>  >So what I would like to know is what I should monitor to get the
>> earliest
>>>  and most consistent notification of updates?
>>>
>>
>>I should have sent this email to wp-hackers the day of launch, but I
>> forgot.
>>But by no means count on that. Follow the WordPress Blog, Trac, your
>>dashboard, etc.
>
> Hey, how about the WP team dusts off and uses the "Release
> Notification" mailing list that is prominently advertised at
> http://wordpress.org/download/ ? Mike
>
>
>
> --
>
> Michael Clark
> http://www.PlanetMike.com
>
> Christmas Music 24 Hours a Day, 7 Days a week
> http://www.ChristmasMusic247.com
>
> "Injustice anywhere is a threat to justice everywhere."
>   - Martin Luther King Jr.
>
>
> ------------------------------
>
> _______________________________________________
> wp-testers mailing list
> wp-testers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-testers
>
>
> End of wp-testers Digest, Vol 70, Issue 3
> *****************************************
>