On Thu, Mar 10, 2011 at 9:03 PM, Chris Hostetter <hossman_luc...@fucit.org> wrote: > The way it gets into the solr docs is via a property file generated by the > build (see the init-forrest-entities, it's setup as a dependency for just > about everything) that forrest then reads. the old release process docs > were specific that the forrest docs needed to be rebuilt *after* running > ant with the specversion set... > >> http://wiki.apache.org/solr/HowToReleaseSlowly >>
No, it looks like you are still confused. i ran init-forrest-entities followed by the forrest regeneration, committed (http://svn.apache.org/viewvc?view=revision&revision=1078685) If i had not done this, then that date would not have said march 6, 2011. So, i did everything correctly here. If you are upset that the specversion variable says, 3.0 (and not say 3.1 or whatever else), that's not the RM's problem. And for the record, this versioning/website update is nothing like lucene. in lucene, these versions etc kept up to date (for example, branch-3x says 3.2 right now). In solr, it seems that things such as these versions are just left for the release manager to deal with? And the release manager is supposed to do things like test tomcat, jetty, and resin? In solr, the website itself in branch_3x was completely out of sync from trunk (someone was just too lazy to backport?), which is why you see "extra" announcements in my commit referenced above, because i had to sync it up. Finally, the absolute most frustrating thing at all was that the legal stuff was completely fucked, including invalid copyright notices that people just committed, i guess these things were committed out of laziness, realizing someone (probably the RM?) will have to fix all this stuff before release. I probably will never do another RC candidate again, due to my complete frustration with what I believe is a fundamentally broken process (no wonder releases are so infrequent), but one good thing did come out of my 20 hours of complete wasted time: I realized that when it comes to third party dependencies and licensing, this stuff has to be taken more seriously. There is no "policeman" for this right now unfortunately, but you can bet I'm gonna start watching commits on this stuff a lot more carefully in the future. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org