I don't know if it's on the Release ToDo list, but we need a Jenkins job for the Ref Guide to be built from branch_7x also.
On Fri, Nov 9, 2018 at 2:24 PM Nicholas Knize <[email protected]> wrote: > Great work guys, and thanks! > > branch_7_6 has been cut and versions updated to 7.7 on branch_7x. Just > the normal reminder: > > - No new features may be committed to the branch. > - > > Documentation patches, build patches and serious bug fixes may be > committed to the branch. However, you should submit *all* patches you > want to commit to Jira first to give others the chance to review and > possibly vote against the patch. Keep in mind that it is our main intention > to keep the branch as stable as possible. > - All patches that are intended for the branch should first be > committed to the unstable branch, merged into the stable branch, and then > into the current release branch. > - Normal unstable and stable branch development may continue as usual. > However, if you plan to commit a big change to the unstable branch while > the branch feature freeze is in effect, think twice: can't the addition > wait a couple more days? Merges of bug fixes into the branch may become > more difficult. > - > > *Only* Jira issues with Fix version "X.Y" and priority "Blocker" will > delay a release candidate build. > > > Also, a quick request. It doesn't look like I have Jenkins admin rights. > Would someone (with the power) either mind granting me admin privileges or > add/update the Jenkins build tasks for the new branch? > > Thank you, > > - Nick > > On Fri, Nov 9, 2018 at 11:43 AM Chris Hostetter <[email protected]> > wrote: > >> >> : I don't have any problem waiting until tomorrow to cut the branch. I >> : noticed a patch was just committed so let me know if you happen to >> resolve >> : this sooner than expected. >> >> Heh .. yeah, since I didn't hear back from you I stayed up a little later >> then usual the last 2 nights re-reviewing everything (that and the >> patch review from smiley gave me some re-assurance.) >> >> (As far as SOLR-12962 is concerned) Feel free to cut branch_7_6 whenever >> you're ready. >> >> >> >> >> : On Thu, Nov 8, 2018 at 3:59 PM Chris Hostetter < >> [email protected]> >> : wrote: >> : >> : > >> : > : Let me know if there are any other blockers that need to be resolved >> : > prior >> : > : to cutting the branch. If not, I will plan to cut the branch on >> Friday or >> : > : (provided they are close to resolution) whenever these issues are >> : > resolved. >> : > >> : > nknize: I'd like to try and get SOLR-12962 into 7.6... >> : > >> : > It's a new "opt in" feature, but one that should help prevent a lot of >> : > performance problems for people who want to try it out -- so I'd >> really >> : > like to release it ASAP so we can hopefully get feedback from folks >> who >> : > try it in time to consider changing the default to "opt out" ~8.0 (see >> : > SOLR-12963 and parent SOLR-8273 for background) >> : > >> : > The patch is currently feature complete -- the only 'nocommits' are >> for >> : > updating a small amount of documentation, which I should have done >> : > sometime thursday morning (GMT-0700). >> : > >> : > I'm currently having my machine hammer on the tests, and >> waiting/hoping >> : > for some patch review / sanity checks. >> : > >> : > >> : > My typically "personal workflow based on comfort level" for a change >> like >> : > this would be to do nothing but testing & self-review for at least a >> day >> : > before committing & backporting ... which would mean wrapping it up >> : > sometime friday afternoon (GMT-0700). >> : > >> : > Unless there are any objections, I'd appreciate knowing if either: >> : > >> : > 1) You would be ok holding off on cutting branch_7_6 until >> : > sometime *after* friday ? >> : > >> : > 2) Folks would be ok w/me backporting SOLR-12962 to banch_7_6 after >> : > you fork it (even though it's a new feature, not a blocker bug >> fix) ? >> : > >> : > >> : > Thoughts? Concerns? >> : > >> : > >> : > >> : > >> : > -Hoss >> : > http://www.lucidworks.com/ >> : > >> : > --------------------------------------------------------------------- >> : > To unsubscribe, e-mail: [email protected] >> : > For additional commands, e-mail: [email protected] >> : > >> : > -- >> : >> : Nicholas Knize, Ph.D., GISP >> : Geospatial Software Guy | Elasticsearch >> : Apache Lucene Committer >> : [email protected] >> : >> >> -Hoss >> http://www.lucidworks.com/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> -- > > Nicholas Knize, Ph.D., GISP > Geospatial Software Guy | Elasticsearch > Apache Lucene Committer > [email protected] >
