[wp-hackers] WordPress 3.0.1 package problem?

[Andrew Nacin]

On Mon, Aug 30, 2010 at 8:53 AM, Lynne Pope <lynne.pope at gmail.com> wrote:

> On Tue, Aug 31, 2010 at 12:17 AM, Rich Pedley <elfin at elfden.co.uk> wrote:
>
> > On 30/08/2010 12:54, Mike Little wrote:
> >
> >> On 30 August 2010 12:48, Rich Pedley<elfin at elfden.co.uk>  wrote:
> >>
> >>  On 30/08/2010 12:40, Mike Little wrote:
> >>>
> >>>   Actually, I just spotted you said wordpress-mu 3.01, there is no
> >>>>>
> >>>> WordPress
> >>>> MU 3.0.1 it's all WordPress now.
> >>>>
> >>>>
> >>> Then why is there a 3.0&  3.0.1 listed in the MU Releases section?
> >>>
> >>> That page is confusing though, would it be better to split into 3 now?
> >>>
> >>> Rich
> >>>
> >>>
> >> The mu releases did not used to be on that page at all. I suspect it's
> >> something to do with the reworking of the .org site. So my guess would
> be
> >> that an automated script that generates the links is probably confused
> by
> >> having mu releases listed on the same page (and now pointing at the same
> >> svn
> >> tree).
> >>
> >>
> > actually thinking about it, having those there is useful for those
> > upgrading from MU.
> >
> >  I still think the page needs splitting into 3 now though.
>

To address the various questions here -

That page can probably be split, yes. We dropped it in there when we shut
down mu.wordpress.org because we didn't want the MU archive to go away.

That said, the 3.0+ "MU" zips are for the 2.9.2- MU automatic upgrade, which
expects the download to be inside a directory called "wordpress-mu" instead
of "wordpress". That's the only difference between 3.0.1-mu-latest and
3.0.1-latest.

Because these are only used by the automatic upgrade, we should be able to
hide them from the release archive page.