> 2) if you build lucene or solr from source, the version in the artifact > names are "3.5-SNAPSHOT" ... last time i checked, a release named "3.5" > would have it's build.xml such that building from source w/o explicitly > setting the version props would result in "3.6-SNAPSHOT" (or > "3.5.1-SNAPSHOT") so it looks like perhaps we forgot to update the version > on the branch before the release? ... either that or maybe there was a > discussion about deliberately changing this that i just didn't notice?
Lucene: The last time this was done was with the 2.1.0 release. From 2.2.0 through 2.4.1, the source release build version was left the same as the release, with no -dev and in most cases not even the proper patch version included (e.g. 2.3.1+ and 2.4.1). The current practice -- leaving the version intact, including the -dev/-SNAPSHOT suffix -- began with the 2.9.1 release. Solr: Prior to the Lucene-Solr development merge, Solr always did the set-the-source-release-version-to-the-next-patch-version thing (with the exception of 1.3, when the version was left the same as the release, very likely not intentionally). Steve
