You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wayang.apache.org by Rodrigo Pardo Meza <rp...@apache.org> on 2022/03/17 19:57:29 UTC
[DISCUSS] RC policy and Deleting branches
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
Re: [DISCUSS] RC policy and Deleting branches
Posted by Bertty Contreras <be...@databloom.ai>.
Hi Folks,
I will create the tags, if then we need the branch we will created from the
tags as @JB recommend
Best Regards,
Bertty
On Sat, Mar 19, 2022 at 3:14 PM Jean-Baptiste Onofré <jb...@nanthrax.net>
wrote:
> We can do this way, another approach is to create the branch on demand
> starting from the release tag.
>
> I agree to tag and clean.
>
> Regards
> JB
>
> On Fri, Mar 18, 2022 at 11:27 AM Christofer Dutz
> <ch...@c-ware.de> wrote:
> >
> > 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 <zk...@yahoo.gr.INVALID>
> > Sent: Freitag, 18. März 2022 09:43
> > To: dev@wayang.apache.org
> > Subject: Re: [DISCUSS] RC policy and Deleting branches
> >
> > Hello,
> > yes, it sounds reasonable.
> > Best
> > --
> > Zoi
> >
> > Στις Πέμπτη 17 Μαρτίου 2022, 10:22:18 μ.μ. CET, ο χρήστης Bertty
> Contreras <be...@databloom.ai> έγραψε:
> >
> > 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 <alo@databloom.ai
> >
> > 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
> > > > <rp...@apache.org>
> > > 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
> > >
> >
>
Re: [DISCUSS] RC policy and Deleting branches
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
We can do this way, another approach is to create the branch on demand
starting from the release tag.
I agree to tag and clean.
Regards
JB
On Fri, Mar 18, 2022 at 11:27 AM Christofer Dutz
<ch...@c-ware.de> wrote:
>
> 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 <zk...@yahoo.gr.INVALID>
> Sent: Freitag, 18. März 2022 09:43
> To: dev@wayang.apache.org
> Subject: Re: [DISCUSS] RC policy and Deleting branches
>
> Hello,
> yes, it sounds reasonable.
> Best
> --
> Zoi
>
> Στις Πέμπτη 17 Μαρτίου 2022, 10:22:18 μ.μ. CET, ο χρήστης Bertty Contreras <be...@databloom.ai> έγραψε:
>
> 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 <al...@databloom.ai>
> 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
> > > <rp...@apache.org>
> > 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
> >
>
Re: [DISCUSS] RC policy and Deleting branches
Posted by jorge Arnulfo Quiané Ruiz <qu...@gmail.com>.
+1 for tagging and cleaning up: I believe this is the easiest and cleanest
way to keep our repo clean.
On Fri, 18 Mar 2022 at 11:27 AM Christofer Dutz <ch...@c-ware.de>
wrote:
> 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 <zk...@yahoo.gr.INVALID>
> Sent: Freitag, 18. März 2022 09:43
> To: dev@wayang.apache.org
> Subject: Re: [DISCUSS] RC policy and Deleting branches
>
> Hello,
> yes, it sounds reasonable.
> Best
> --
> Zoi
>
> Στις Πέμπτη 17 Μαρτίου 2022, 10:22:18 μ.μ. CET, ο χρήστης Bertty
> Contreras <be...@databloom.ai> έγραψε:
>
> 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 <al...@databloom.ai>
> 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
> > > <rp...@apache.org>
> > 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
> >
>
>
RE: [DISCUSS] RC policy and Deleting branches
Posted by Christofer Dutz <ch...@c-ware.de>.
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 <zk...@yahoo.gr.INVALID>
Sent: Freitag, 18. März 2022 09:43
To: dev@wayang.apache.org
Subject: Re: [DISCUSS] RC policy and Deleting branches
Hello,
yes, it sounds reasonable.
Best
--
Zoi
Στις Πέμπτη 17 Μαρτίου 2022, 10:22:18 μ.μ. CET, ο χρήστης Bertty Contreras <be...@databloom.ai> έγραψε:
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 <al...@databloom.ai>
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
> > <rp...@apache.org>
> 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
>
Re: [DISCUSS] RC policy and Deleting branches
Posted by Zoi Kaoudi <zk...@yahoo.gr.INVALID>.
Hello,
yes, it sounds reasonable.
Best
--
Zoi
Στις Πέμπτη 17 Μαρτίου 2022, 10:22:18 μ.μ. CET, ο χρήστης Bertty Contreras <be...@databloom.ai> έγραψε:
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 <al...@databloom.ai>
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 <rp...@apache.org>
> 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
>
Re: [DISCUSS] RC policy and Deleting branches
Posted by Bertty Contreras <be...@databloom.ai>.
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 <al...@databloom.ai>
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 <rp...@apache.org>
> 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
>
Re: [DISCUSS] RC policy and Deleting branches
Posted by Alexander Alten-Lorenz <al...@databloom.ai>.
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 <rp...@apache.org> 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