I see that trunk works on Java 1.7, which is kind of an impediment for me right now.
Under which cases fixes/features go to a branch rather than trunk? Would this case be an example? Like working on branch lucene_solr_4_7 rather than trunk? Thanks again On Tue, Apr 1, 2014 at 10:44 AM, Shai Erera <ser...@gmail.com> wrote: > In general you should checkout 'trunk' and fix/add stuff there. The > community will then decide whether the feature/fix should also be > backported to 4.x (very likely) and whether a 3.x releases is also needed > (very unlikely). > > Shai > > > On Tue, Apr 1, 2014 at 4:39 PM, Fermin Silva <silvafe...@gmail.com> wrote: > >> Hi all, >> >> I found a possible feature addition to the ReplicationHandler class plus >> some fixes to allow better extension/subclassing of this file. >> >> I'd like to contribute but I'm unsure about the steps required. >> Firstly, I should create a JIRA ticket, I'm OK with that. >> Secondly, I should checkout a branch, do the fixes and post the patch. >> >> Now, which branch should I checkout ? >> The fix I'd like to contribute applies to SOLR 3.5.x, which is our >> production version, but I'm sure that's a bit obsolete. >> Also, I'm not sure if SOLR 4.x branch still uses the same kind of >> replication, let alone trunk, which heads to SOLR 5.x. >> >> So, which branch you think I should checkout? Should I also backport or >> *'forwardport'* to other branches ? >> >> Thanks in advance >> -- >> Fermin Silva >> > >
