forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <rgard...@apache.org>
Subject Issue review
Date Sat, 31 Mar 2007 21:39:58 GMT
The deadline for the Release Plan Vote is Monday 2007-04-01 at 22:00 
UTC, a little under 24 hours from now (as of writing this mail).

So, I thought a review of outstanding issues may be useful. First, I 
think we deserve a collective pat on the back for getting from around 25 
issues to 7 in such a short amount of time. I wonder why we couldn't get 
it together before? (lets discuss that *after* release though).

Outstanding issues are:

Blocker
-------

FOR-911  	decide content of release

I think we are agreed on this. See 
http://marc.info/?l=forrest-dev&m=117507344924498&w=2
Lazy consensus applies.

FOR-868 	add relevant notes to the "Upgrading" xdoc 	

Needs attention

FOR-855 	verify the license situation prior to each release 	

Assigned to David, there has been plenty of activity here, thanks David.

Critical
--------

FOR-742 	trouble accessing unversioned plugin for a released

Assigned to Cyriaque (are you still driving this or is this from when 
you were working on the build files for this issue?)

This issue is complete, but we need to verify that all plugins are 
available from the correct download location and we need to test against 
the release candidate. There should be no need to touch the code on 
this, so OK to do even in the code freeze.

Major
-----

FOR-644 	code-style cleanup for xml files 	

David suggests doing this during the code freeze (it will only affect 
whitespace)

FOR-241 	character entities (e.g. ampersand) are expanded again

This looks like a Cocoon issue and affects a very specific use case. We 
may have to let this slip to 0.9

FOR-922 	update all docs that explain sitemap fragments 	

David has provided comments warning the reader, Ferdinand has done some 
work on one of our main How-To documents. I'm happy for this to slip to 
0.9 if necessary (it is only a documentation issue so our published docs 
will reflect the change before 0.9 is released).

Conclusion
==========

We are in a really good shape to actually hit the schedule outlined in 
David release plan.

Ross

Mime
View raw message