For Solr, we can just move the current trunk to a 15 branch.
-Yonik
On Tue, Mar 23, 2010 at 9:39 AM, Grant Ingersoll wrote:
>
> On Mar 22, 2010, at 8:27 AM, Uwe Schindler wrote:
>
>> Hi all,
>>
>> the discussion where to do the development after the merge, now gets actual:
>>
>> Currently a luso
On Mar 22, 2010, at 8:27 AM, Uwe Schindler wrote:
> Hi all,
>
> the discussion where to do the development after the merge, now gets actual:
>
> Currently a lusolr test-trunk is done as a branch inside solr
> (https://svn.apache.org/repos/asf/lucene/solr/branches/newtrunk). The
> question is,
This looks good to me.
+1 on landing flex now.
On 03/22/2010 08:27 AM, Uwe Schindler wrote:
Hi all,
the discussion where to do the development after the merge, now gets actual:
Currently a lusolr test-trunk is done as a branch inside solr
(https://svn.apache.org/repos/asf/lucene/solr/branche
On Mar 22, 2010, at 8:27 AM, Uwe Schindler wrote:
> Hi all,
>
> the discussion where to do the development after the merge, now gets actual:
>
> Currently a lusolr test-trunk is done as a branch inside solr
> (https://svn.apache.org/repos/asf/lucene/solr/branches/newtrunk). The
> question is,
Hi all,
the discussion where to do the development after the merge, now gets actual:
Currently a lusolr test-trunk is done as a branch inside solr
(https://svn.apache.org/repos/asf/lucene/solr/branches/newtrunk). The question
is, where to put the main development and how to switch, so non-devel
