[wp-hackers] 2.0 branch

[Alex Günsche]

I read the below post last week before I left for a small vacation, and
I really hoped it would raise some discussion. I agree with Bas that
those are very important issues for all people who need and apprechiate
WP 2.0.x as a "stable" distribution. (For example, I use only 2.0.x for
myself and for customer projects, as I couldn't guarantee consistency
accross upgrades with the later series.)


Best regards,
Alex


On Sat, 2007-07-21 at 16:21 +0200, wordpress at nazgul.nu wrote:
> I've got a few questions/remarks about the 2.0 branch:
> 
> 1. When will 2.0.11 be released? A couple of serious security bugs were
> found and fixed and a couple of RC's were released, but that's been over 3
> weeks [1] ago.
> 
> 2. At the moment it looks like only security related patches get into the
> 2.0 branch. What's going to happen with all those 2.0.eventually tickets
> [1]. Some of them have been around for 5 2.0 branch releases. We should
> either commit them, or kill the milestone.
> 
> 3. If it's true that only security fixes go into the 2.0 branch, how do we
> handle non-security tickets [3] submitted by Debian? They are the main
> reason we still support the 2.0 branch.
> 
> The above is not intended to step on anybodies toes, but I'd like to get
> some discussion/policy making going on how we handle that branch. At the
> moment it's kind of vague to me and I assume to others as well. 
> 
> Regards,
> Bas Bosman (Nazgul)
> 
> [1] http://trac.wordpress.org/changeset/5768 
> [2]
> http://trac.wordpress.org/query?status=new&status=assigned&status=reopened&m
> ilestone=2.0.eventually&order=priority 
> [3] http://trac.wordpress.org/ticket/4618 

-- 
Alex Günsche, Zirona OpenSource-Consulting
http://www.zirona.com/ | Hilfe für das HQ AC: http://www.prohq.de
PubKey for this address: http://www.zirona.com/misc/ag.ml2007.asc