[Evergreen-dev] [Eg-newdevs] Release branch proposal

[Galen Charlton]

Hi,

On Mon, Feb 26, 2024 at 11:02 AM Jane Sandberg via Eg-newdevs <
eg-newdevs at list.evergreen-ils.org> wrote:
> My proposal would be to make all needed changes to the release series
branch,
> and then create the tag branch directly from the release series branch
when all
> these steps are done.  So, at the time of release, rel_3_12 and
tags/rel_3_12_2
> would be identical, before rel_3_12 starts to accumulate bug fixes for
the next release.

I'm overall in support of the proposal.

If we move away from tag branches, I strongly advocate for using Git tags
instead to represent the full release (and to enforce some discipline on us
to apply a new tag if we discover that a release was a brown bag). We do
this for OpenSRF, and Koha does it successfully as well.

One thing that I suggest is that we also consider dropping ChangeLog files
outright, or if somebody is still using them from the tarballs, to generate
just for the tarball. The release notes are what gets actually read by
humans (and it would be easy to symlink from the release notes to ChangeLog
if really needed). However, if anybody is actually reading (or possibly
more likely, parsing the ChangeLog files) in its current form, please speak
up.

Here's a piece that advocates against what we're currently doing to
generate ChangeLog https://keepachangelog.com/en/0.3.0/

> It would eliminate any errors that could arise through
> differences in the release series branch and the release
> tag branch (e.g. not forward-porting the upgrade script to rel_3_12)

But note that we'll still need to do some forward-porting, but from series
branches up to main.

> Having these things in the release series branch may cause some kind of
>  problem that I'm not familiar with.

I think the main thing will be ensuring that any tooling that updates the
version numbers is rock solid. We might also consider, immediately after
doing a release, doing a commit that updates the version numbers again to
clearly indicate that the series branch is back to a pre-next-version mode.

Regards,

Galen
--
Galen Charlton
Implementation and IT Manager
Equinox Open Library Initiative
gmc at equinoxOLI.org
https://www.equinoxOLI.org
phone: 877-OPEN-ILS (673-6457)
direct: 770-709-5581
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.evergreen-ils.org/pipermail/evergreen-dev/attachments/20240226/eb946757/attachment.htm>