Greg: You can commit it into the solr_lucene_5_2 branch as well as trunk and 5x and it does what you want. If there's a 5.2.2 release someone will set a label on the 5_2 branch.
There needs to be a 5.2 label in JIRA though, you're right there. Erick On Wed, Jun 17, 2015 at 4:43 PM, Gregory Chanan <[email protected]> wrote: > I didn't see any discussion on if we should commit to that branch or not and > don't know if we have a general policy. My thought process was: > - If there ends up being a 5.2.2 release, it would be nice to have that in > - If there doesn't end up being a 5.2.2 release, no real harm > - The code is fresh in my mind, better to put it in now rather than wait > until a release is decided or not > > Greg > > On Wed, Jun 17, 2015 at 3:56 PM, Anshum Gupta <[email protected]> > wrote: >> >> Yes, if we're committing to lucene_solr_5_2 now, we should. >> >> On Wed, Jun 17, 2015 at 3:49 PM, Gregory Chanan <[email protected]> >> wrote: >>> >>> Should we add a 5.2.2 version to jira? I committed SOLR-7688 to >>> lucene_solr_5_2 but can't make it as a fixVersion in jira. >>> >>> Thanks, >>> Greg >> >> >> >> >> -- >> Anshum Gupta > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
