[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: Stable kf5 branch created for kxstitch release-2.2.0
From:       Steve Allewell <steve.allewell () gmail ! com>
Date:       2019-05-20 19:54:19
Message-ID: 6dbe7687-cb46-b6e7-c5f6-850a74a62fe9 () gmail ! com
[Download RAW message or body]

Hi Albert, thanks for the feedback.

This is intended as a release branch and I have named my release branches like this \
for years.  Generally I do a new major.minor branch for each release with any \
maintenance patches in the same branch.  These are then tagged with the release \
version number.

I appreciate this may not be how others work, but it is something I am happy with \
unless there is perhaps something detrimental with this method - always happy to be \
pointed in the right direction.

Best regards


Steve


On 19/05/2019 22:38, Albert Astals Cid wrote:
> El diumenge, 19 de maig de 2019, a les 23:35:12 CEST, Albert Astals Cid va \
> escriure:
> > El diumenge, 19 de maig de 2019, a les 15:18:06 CEST, Steve Allewell va escriure:
> > > I have created and pushed a new git branch for kxstitch called release-2.2.0
> > 
> > That really more a release name than a branch name, wouldn't make more sense for \
> > it be called something like 2.2.x ? 
> > I mean the point of stable branches is that you do there the stable development \
> > for that branch, if you want to release a 2.2.1 will you make a new stable branch \
> > called release-2.2.1? In what way would it be different from release-2.2.0 except \
> > it has more fixes?
> 
> On the other hand Luigi already did the change so if you don't really plan to do a \
> 2.2.1 don't change the branch name, just thought for the future :) 
> Cheers,
> Albert
> 
> > 
> > Cheers,
> > Albert 
> > 
> > > 
> > > Please begin tracking this branch for stable kf5 translations.
> > > 
> > > String freeze date is 31st May with an expected release date of the
> > > 7th June.  If any translation teams require longer than that, please
> > > let me know.
> > > 
> > > Many thanks
> > > 
> > > Steve
> > > 
> > 
> > 
> > 
> > 
> > 
> 
> 
> 
> 
> 


[prev in list] [next in list] [prev in thread] [next in thread]