I'm not sure how this would be done and I don't want to take away
from the great work done on the Wiki, but some type of versioning is
needed so that we know what version of the wiki corresponds to what
release (now that we have a few releases). I know from legal (see
the legal-discuss archives) that you can't include the wiki dump in
the release, but I am sure there is no reason why we can't at least
create a copy of the pages at release time and still host them on the
wiki.
Just my two cents,
Grant
On Jun 18, 2007, at 6:23 PM, Chris Hostetter wrote:
Lucene-Java currently has a 2.2 release candidate available, and
people
are already talking about having a release post-mortem discussion to
discuss what worked well/badly in the rleease process, and make
sure the
process documentation is up to date.
The reminded me that i wanted ot suggest the same thing about our 1.2
release ... while we were reviewing the release candiates, i put some
notes at the bottom of the release wiki to revist ... does anyone else
have any thoughts on the process as it actually happened versus the
process as written? any suggestions for changing the process in
general
for hte next release?
http://wiki.apache.org/solr/HowToRelease
Even if we don't spend a lot of time changing the process steps now,
making notes at teh bottom of things we want to consider changing
in the
future will help jog our memories the next time we start to think
about
doing a release.
(Yonik: you're relaly in the best position to answer some of these
questions since you had to do 99% of the work on both the 1.1 nad 1.2
release)
-Hoss
