"Anything currently in the trunk ..."
I think you mean "Anything in the 4x branch", since "trunk" is 5x by
definition.
But I'd agree that taking a nightly build or building from the 4x branch is
likely to be a better bet than the "old" Alpha.
-- Jack Krupansky
-----Original Message-----
From: Erick Erickson
Sent: Sunday, July 15, 2012 11:02 AM
To: solr-user@lucene.apache.org
Subject: Re: 4.0.ALPHA vs 4.0 branch/trunk - what is best for upgrade?
Anything currently in the trunk will most probably be in the BETA and
in the eventual release. So I'd go with the trunk code. It'll always
be closer to the actual release than ALPHA or BETA....
I know there've been some changes recently around, exactly
the "collection" name. In fact there's a discussion about
rearranging the whole example directory....
Best
Erick
On Sat, Jul 14, 2012 at 9:54 PM, Roman Chyla <roman.ch...@gmail.com> wrote:
Hi,
Is it intentional that the ALPHA release has a different folder structure
as opposed to the trunk?
eg. collection1 folder is missing in the ALPHA, but present in branch_4x
and trunk
lucene-trunk/solr/example/solr/collection1/conf/xslt/example_atom.xsl
4.0.0-ALPHA/solr/example/solr/conf/xslt/example_atom.xsl
lucene_4x/solr/example/solr/collection1/conf/xslt/example_atom.xsl
This has consequences for development - e.g. solr testcases do not expect
that the collection1 is there for ALPHA.
In general, what is your advice for developers who are upgrading from solr
3.x to solr 4.x? What codebase should we follow to minimize the pain of
porting to the next BETA and stable releases?
Thanks!
roman
