Our current release process works like this: About a month before the release, create the “open-release/release-name.master” branch from the master branch. Let’s call this the release-master branch. Testing and fixes happen on the release-master branch Once everything is working and stable, we tag…

Tagging releases? Useful or not?

jill (Jillian Vogel) September 22, 2020, 5:16am 5

We’ve relied on the tagged named releases to help old instances through breaking database migrations, see Migrate from Eucalyptus to Juniper, but I believe that’s the only reason.

Topic		Replies	Views
Should we rename the release branches? Build-Test-Release	11	939	May 13, 2024
Juniper.2 has been tagged Releases	0	948	July 13, 2020
Juniper.3 has been tagged Releases	2	825	August 27, 2020
We are a few days from creating Juniper master branches Build-Test-Release juniper	4	666	May 25, 2020
Build-Test-Release Biweekly 2021-02-15 Build-Test-Release	1	472	February 24, 2021

Tagging releases? Useful or not?

Related topics