apache / apache/lucene

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

Open
#9,966 5 comments 0 reactions 0 assignees View on GitHub
legacy-jira-priority:Minor type:bug
Dominant language
Java
Stars
3.6k
Forks
1.4k
Avg merge
2d 11h
Merged PRs (30d)
88

Description

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.

---
Migrated from [LUCENE-8923](https://issues.apache.org/jira/browse/LUCENE-8923) by Ignacio Vera (@iverase)
Attachments: [LUCENE-8923.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-8923/LUCENE-8923.patch)

Contributor guide

Open the contributing guide

Research direction

Start by reading the release procedure and the CHANGES.txt update described in the issue, then inspect the attached LUCENE-8923.patch for prior context. Confirm how the minor version branch is updated and determine the equivalent master behavior; done means a release adds the new version to CHANGES.txt in master as well.

Written by the indexing model from the issue text.

Assessment

Domain
release
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.