In PLC4X we usually keep the release branches open ...
So, we can offer bugfix releases for previously released versions.
All of our release branches have the same prefix
rel/{major-version}.{minor-version}
As you can see the name doesn't contain a bugfix version as this is what the
tags are then for.
But I guess if the tags remain in the repo, that's also ok to remove the branch.
Chris
-----Original Message-----
From: Zoi Kaoudi <[email protected]>
Sent: Freitag, 18. März 2022 09:43
To: [email protected]
Subject: Re: [DISCUSS] RC policy and Deleting branches
Hello,
yes, it sounds reasonable.
Best
--
Zoi
Στις Πέμπτη 17 Μαρτίου 2022, 10:22:18 μ.μ. CET, ο χρήστης Bertty Contreras
<[email protected]> έγραψε:
Hello Folks,
I think to maintain clean the repository is important, and using the tag will
help with it :D
I agree for tagging and cleaning up too :D
Best regards,
Bertty
On Thu, Mar 17, 2022 at 9:11 PM Alexander Alten-Lorenz <[email protected]>
wrote:
> Hi all,
>
> Good point. I’d vote for tagging and cleaning up after a release.
>
> Thanks for bringing this up,
> —Alex
>
> Sent from my iPhone
>
> > On 17. Mar 2022, at 20:57, Rodrigo Pardo Meza
> > <[email protected]>
> wrote:
> >
> > Good evening folks,
> >
> > We have been trying to clean the existing branches in our
> > Repository. In this situation we found that there exist 7 branches
> > with release
> candidates.
> >
> > Considering that after the release there are no more commits on
> > those Branches generated for the RCs. Does it make any sense to keep
> > those branches there? Should we simply delete them?
> >
> > For future releases, it might be better if each Release Candidate is
> > a
> TAG.
> > And finally, while preparing the final release, we create a branch.
> >
> > Best regards!
> >
> > Rodrigo
>
