search

mikemccand / stargazers-migration-test

Testing Lucene's Jira -> GitHub issues migration
0 stars 0 forks source link

Release procedure does not add new version in CHANGES.txt in master [LUCENE-8923] #920

Open mikemccand opened 5 years ago

mikemccand commented 5 years ago

This issue is just to track something that maybe missing in the release procedure. It currently adds a new version on CHANGES.txt in the minor version branch but it does not do it in master.

Legacy Jira details

LUCENE-8923 by Ignacio Vera (@iverase) on Jul 17 2019 Attachments: LUCENE-8923.patch

mikemccand commented 5 years ago

In the meanwhile I propose to create them manually. Attached a patch.

@mocobeta I am moving you issues to Lucene 8.3 in master, let me know if it is correct.

[Legacy Jira: Ignacio Vera (@iverase) on Jul 17 2019]

mikemccand commented 5 years ago

+1 Even if some changes are missing I think we'd benefit from pushing this rather soon so that developers don't automatically add their changes to 8.2 as the last minor.

[Legacy Jira: Adrien Grand (@jpountz) on Jul 17 2019]

mikemccand commented 5 years ago

Commit 41ae03a9a0dedd41865d5e6200fa1a73c8ee7b7f in lucene-solr's branch refs/heads/master from Ignacio Vera https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=41ae03a

LUCENE-8923: Add Lucene-8.3 entry in CHANGES.txt

[Legacy Jira: ASF subversion and git services on Jul 17 2019]

mikemccand commented 5 years ago

I added the entries. I leave the issue open so we can clarify if the current procedure needs to be updated to add this entries,

[Legacy Jira: Ignacio Vera (@iverase) on Jul 17 2019]

mikemccand commented 5 years ago

I am moving you issues to Lucene 8.3 in master, let me know if it is correct.

It's correct, thank you!

[Legacy Jira: Tomoko Uchida (@mocobeta) on Jul 17 2019]