On 18/12/2008, at 8:07 PM, Ralph Goers wrote:
On Dec 18, 2008, at 12:42 AM, Brett Porter wrote:
Hi,
I did what seems like my bi-annual review of all the unscheduled
issues today, reviewing and scheduling where appropriate. There's
10 left with open questions, and I'm making an early new years
resolution to keep on top of new reports :)
Jason, Shane - as instructed I put all the reported regressions
with trunk into 3.0-alpha-3. I expect some of these are already
fixed so it would be worth a run through them before releasing
alpha-1 to see if some can be closed out.
However, the main purpose was to identify reported regressions in
2.1.0-M1, of which we have a couple. So 2.1.0-M2 is down to about
11 issues including some patches to review. I updated the roadmap,
moving Doxia to M3 as they round out the 1.1 release. I also moved
the MNG-624 out to 2.2 (or beyond) while Ralph reviews his
implementation.
Given enough time to wrap these up, I'd like to shoot for an M2
release by the end of the year. M3 and M4 could follow quickly
since the work is already done on branches.
Cheers,
Brett
Frankly, I haven't really done much with 624 since ApacheCon
primarily because I got the impression that 2.1 has stalled and 3.0
is going to beat it out. Since I've been told that the issue will be
fixed in 3.0 I wasn't sure it would be worth the effort. If 2.1 is
going to pick up momentum then I will look at fixing the problems
during my time off during Christmas.
Cool... it'd certainly be better to have it in 2.1 if the problems can
be sorted out given the popularity of the issue :)
Cheers,
Brett
--
Brett Porter
[email protected]
http://blogs.exist.com/bporter/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
