Chris Hostetter wrote: > : I just created the release artifacts (incl. maven artifacts) from the > : 2.3 branch and uploaded the files to > : http://people.apache.org/~buschmi/staging_area/lucene_2_3/rc1/. > > Some misc comments while purusing the release artifacts... > > 1) the release release should use the version number "2.3.0" (note the > trailing ".0" to be consistent with most of the previous releases (1.9 was > called 1.9-final for some reaso) > > 2) the CHANGES.txt file needs updated on the branch to replace "trunk" > with 2.3.0 and the release date (once it's picked)
Thanks. I didn't update CHANGES.txt yet because I wasn't sure about the exact release date. I'll make sure to use version 2.3.0 and to update CHANGES.txt when I make the final release. > 3) that anoying "fake" UTF8 BOM is in the CHANGES.txt file on both the > trunk and in the release (it makes 'less' think it's a binary file). Can we just remove it? > 4) as a result of the changes made to how "nightly" and historic javadocs > are linked to on the site since 2.2, the local javadocs included with the > release are only linked to from the "Resources:Developers" section of the > local docs (/lucene-2.3-rc1/docs/developer-resources.html) and are refered > to as "Nightly Build Javadocs" ... when viewing the > "Documentation:Javadocs" page the "Javadocs for Official Releases" section > does not list 2.3. > > (for this release, we may just want to manually change the forrest docs on > the branch ... but this seems like a maintence pain moving forward, so we > may want to think about an alternate way of dealing with this) OK, I'll update the docs. > 5) i just noticed that in the binary releases, the contrib directories do > not contain the README.txt files ... looks like this was true in 2.2.0 as > well ... we should probably fix this (but it's not a show stopper) OK, I'll take a look to figure out what happened to the README.txt files. Thanks for finding and explaining these issues, Hoss!! -Michael --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
