cpoerschke commented on pull request #1571: URL: https://github.com/apache/lucene-solr/pull/1571#issuecomment-728089734
> ... I assume we merge to master squashing and then cherry-pick the commit to some other branches? ... Yes, squash-and-merge to master branch and then cherry-pick to branch_8x from which branch_8_8 would be cut in due course as part of the 8.8.0 release process. > ... Do you think we need to target a major release? Or we could add it in the upcoming minors? ... Good question. * From end users' perspective there are no breaking changes which would point towards targeting 9.x major rather than 8.8+ minor releases. * From code API perspective, there are some APIs that changed but from what I can see -- https://github.com/cpoerschke/lucene-solr/commits/feature/SOLR-14560-cpoerschke-2 has associated commits -- we could provide backwards compatible deprecated niceties to avoid breaking builds for anyone who perhaps had created their own transformer or plugin class that referenced the changed APIs. Having said that, perhaps for `solr/contrib` code the expectations of not breaking APIs in a given 8.x series are different from `solr/core` code. * But yes, with or without backcompat niceties, I think we can target the 8.8.0 minor rather than then 9.0 major release. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
