Re: [Gimp-docs] release procedure

On Thu, Jun 14, 2012 at 10:15:54AM +1000, Roman Joost wrote:
> On Wed, Jun 13, 2012 at 05:18:26PM -0300, Joao S. O. Bueno wrote:
> > I think some organization to get it going is indeed necessary - and
> > this one - "two weeks for updating translation"  is certainly better than none.
> > 
> > So, +1 from me.
> Sounds good to me as well: +1
> Basically that means, for each release we create a branch. Every
> translator has to "finish" his work on this release branch, until it can
> be tagged and the tarballs are created.


> Another possibility is not to create a branch, but simply use an
> announcement mail (which is probably good anyway) to mark the upcoming
> release.

Yes but in this way you force to stop working on the main document.

Instead if you create a branch you freeze for the translator and the
work on HEAD could go forward without messing up the translations.

This is the concept.


Marco Ciampa

| Linux User  #78271 |
| FSFE fellow   #364 |

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]