[wp-hackers] Version Maintenance

[Viper007Bond]

I believe 2.1 is the recommended version while 2.0.x will be like 1.5.x was
-- security fixes and minor bug fixes, but nothing new content wise.

But yes IMO, there should be a new, separate page (as to not encourage it's
new use) for 2.0.x for those who don't want to upgrade.

On 1/23/07, Dougal Campbell <dougal at gunters.org> wrote:
>
> Since we're now maintaining the 2.0 branch for an extended time,
> alongside 2.1, and we presumably will be maintaining 2.0, 2.1, and 2.2
> simultaneously in the future, don't we need to modify the wordpress.org
> downloads page to reflect the availability of these branches?
>
> I thought of this when I was getting ready to update the WordPress entry
> for freshmeat.net. I want set up these different version tracks as
> branches on FreshMeat, but to do that, I need to be able to point at
> download URLs and such for the specific versions. We *have* those URLs,
> but they just aren't documented well on the primary web site. The
> FreshMeat moderators might reject the new branch entry if they can't
> easily verify some of the info.
>
> While we're updating the download info, do we want to point at the
> Debian packages, FreeBSD port, etc.?
>
> Oh, and did anybody ever send a release notification to the
> announcements mailing list?
>
> --
> Dougal Campbell <dougal at gunters.org>
> http://dougal.gunters.org/
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>



-- 
Viper007Bond | http://www.viper007bond.com/