Re: [Gimp-docs] Release procedure (was: Testers requested for our new Mac OS X DMG release!)
Hi, no reply yet. I asked the devs to discuss it at the LGM, but so far I don't see anything in the (intermediate state of) the meeting minutes. Was it discussed and to which result? Greetings Sven -- ___ gimp-docs-list mailing list gimp-docs-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-docs-list
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. Yes. 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 | ++ ___ gimp-docs-list mailing list gimp-docs-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-docs-list
Re: [Gimp-docs] release procedure
On Wed, Jun 13, 2012 at 06:24:44PM +0200, Marco Ciampa wrote: Sorry if I sound a little bit a bureaucrat but I want to propose a rule for the version releases, similar to the string freeze for the programs. Sometimes the manual reach a state the could be safely published. When we decide that that time is reached, I propose to publish a Request For Publication, here in this list, that means that the version branch is created (say gimp-2.8.1 for example..) and the tar balls are delayed for as long as 2 weeks. In that period of time, translators can try do updated and finish their work to reach a, as far as possible, complete multilanguage version of the manual. This is a kind of RFC :-) please say what you think about it. Explicitely requesting a new release seems to be a good idea. (Unless a new major version (2.10.0 or 3.0.0) is released, we don't need a new branch, just a tag for the new release - and even this is not really necessary.) Ulf -- Sie vernichten Getreide - und sammeln Brot für die Welt. -- Karlheinz Deschner ___ gimp-docs-list mailing list gimp-docs-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-docs-list
