[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 2.16 release candidate 3 out
From: |
Francisco Vila |
Subject: |
Re: 2.16 release candidate 3 out |
Date: |
Fri, 24 Feb 2012 00:46:28 +0100 |
2012/2/17 Graham Percival <address@hidden>:
> I've released release candidate 3. There always seems to be
> confusion about this, so let's go over what this means:
>
> - activity on master goes on as normal.
>
> - nobody touches the release/unstable branch, than translators,
> who may merge with that if they want to and don't break
> anything.
I am going to merge lilypond/translation into release/unstable, but I
don't want to lose those translations for master and 2.17. I could
either A) also merge lilypond/translation into staging as usual, or B)
wait for anyone else to merge release/unstable into staging (I see
that it has been done already once).
Are those options correct? Which is best?
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com