On Sat, 26 Nov 2022 at 23:25, Gary Gregory <[email protected]> wrote: > > This is not something to automate IMO, it is just part of the release steps > the RM needs to take, which only happens when you wrap up releasing. Unless > I am misunderstanding something.
The default branch of commons component repo should always refer to a SNAPSHOT version. Only the RC branch(es) should ever be a non-SNAPSHOT version. After a release, the RM should update the default branch to the next SNAPSHOT version. The default branch must never point to a non-snapshot version. > Gary > > On Sat, Nov 26, 2022, 16:50 Xeno Amess <[email protected]> wrote: > > > or would you mind if I make one？ > > ________________________________ > > From: Xeno Amess <[email protected]> > > Sent: Sunday, November 27, 2022 2:29:53 AM > > To: Commons Developers List <[email protected]> > > Subject: Re: [ALL][COMPRESS] POM version > > > > good and could we add a ci checker for this？ > > ________________________________ > > From: Gary Gregory <[email protected]> > > Sent: Saturday, November 26, 2022 8:36:10 PM > > To: Commons Developers List <[email protected]> > > Subject: [ALL][COMPRESS] POM version > > > > Hi all and release managers, > > > > A reminder that a POM version should never be a non-snapshot version in a > > git master branch as I've just found in Compress with 1.22 in the POM. It's > > now 1.23-SNAPSHOT. > > > > Also remember to update the date and description in changes.xml, which I've > > also fixed. > > > > Happy Thanksgiving to folks in the US, > > Gary > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
