RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

branches

This discussion is connected to the gimp-docs-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

4 of 7 messages available
Toggle history

Please log in to manage your subscriptions.
branches Alexandre Prokoudine 12 Dec 21:35
  branches Roman Joost 18 Dec 03:02
   200912191259.01230.ude88@we... Ulf-D. Ehlert 19 Dec 12:58
    branches Alexandre Prokoudine 28 Dec 00:53
     branches Ry?Ta SimaMoto 28 Dec 06:48
      200912282108.13925.ude88@we... Ulf-D. Ehlert 28 Dec 21:08
     200912282105.20600.ude88@we... Ulf-D. Ehlert 28 Dec 21:05
Alexandre Prokoudine
2009-12-12 21:35:17 UTC (almost 15 years ago)

branches

Hi,

This is probably the silliest question on the list ever, but what branch should I be working on in case of subsequent releases for GIMP 2.6?

Alexandre

Roman Joost
2009-12-18 03:02:57 UTC (almost 15 years ago)

branches

On Sat, Dec 12, 2009 at 11:35:17PM +0300, Alexandre Prokoudine wrote:

Hi,

This is probably the silliest question on the list ever, but what branch should I be working on in case of subsequent releases for GIMP 2.6?

IMHO that's why we created the gimp-help-2-6-0 branch for. That's also where your changes should go in. But I think that only applies if you have to change the XML content or add translations for descriptions which are valid for 2.6.

I do have to admit that I lost track of this. Hope it's not gonna end in a big cock up...

Cheers,

Alexandre Prokoudine
2009-12-28 00:53:09 UTC (almost 15 years ago)

branches

On 12/19/09, Ulf-D. Ehlert wrote:

Using the branch after releasing html packages doesn't make any sense to me.

Really? :)

Let's see. We have a stable 2.6 version of GIMP and unstable 2.7 that will become v2.8. So we are dealing with two branches to document. In case we are going to release docs for 2.8 around actual 2.8 release, how on Earth are we supposed to provide updates for 2.6 all this time if not by working on two branches? :)

Of course, if we are not going to release updates for 2.6 or if we are going to start work on for 2.8 *after* 2.8 release, that's a whole different situation :)

Alexandre

Ry?Ta SimaMoto
2009-12-28 06:48:09 UTC (almost 15 years ago)

branches

Hi,

We may prefer to have at least three branches: * a temporary branch, which is specified its its micro version like 2.6.1, only for translation works -- of course any changes on src/ is prohibited; * 2.6 or the MASTER, for editing English source text as well as PO files, and image files;
* 2.7 for preparing for 2.8 (the next master current), it will be now English only.

When the temporary branch is removed after its html package was released, the next release schedule will be more interesting. Perhaps it can be when the documentation of some functions are finished: plug-in-antialias, script-fu-weave, script-fu-clothify, script-fu-sota-chrome-it, script-fu-difference-clouds, python-fu-foggify, script-fu-spyrogimp, script-fu-circuit, script-fu-line-nova, script-fu-lava, script-fu-blend-anim, script-fu-spinning-globe, script-fu-burn-in-anim, script-fu-ripply-anim, and script-fu-waves-anim as well as some mock-ups (script-fu-alien-neon-logo-alpha, script-fu-blended-logo-alpha, script-fu-comic-logo-alpha, script-fu-gradient-bevel-logo-alpha, and script-fu-textured-logo-alpha).

Bye -=-=-=-=-=
SimaMoto,Ry?Ta
http://code.google.com/p/gimp-doc-ja/