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

Featured content

documenting 2.8

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.

2 of 2 messages available
Toggle history

Please log in to manage your subscriptions.
documenting 2.8 Alexandre Prokoudine 07 Sep 13:10
  documenting 2.8 Ulf-D. Ehlert 08 Sep 19:05
Alexandre Prokoudine
2011-09-07 13:10:52 UTC (about 13 years ago)

documenting 2.8

Hi,

It looks like 2.8 is a couple of months away. Personally I'm ready to start documenting new stuff, but not sure if I should do it in master. We've had some big translation commits lately, so how about:

1. Branching the current state now to make a new release later this month (everyone can commit translation updates to the branch until the release)
2. Starting to work on new docs?

Alexandre Prokoudine http://libregraphicsworld.org

Ulf-D. Ehlert
2011-09-08 19:05:22 UTC (about 13 years ago)

documenting 2.8

Am Mittwoch, 07. September 2011, 17:10:52 schrieb Alexandre Prokoudine:

It looks like 2.8 is a couple of months away. Personally I'm ready to start documenting new stuff, but not sure if I should do it in master. We've had some big translation commits lately, so how about:

1. Branching the current state now to make a new release later this month (everyone can commit translation updates to the branch until the release)
2. Starting to work on new docs?

A new 2.6 branch seems to be the easiest way to me.

(Maybe making a new branch for GIMP-2.8 docs and later merging it with the master branch is "more logical" - since GIMP-2.8 is not released. But if merging fails ...)

Ulf

PS: If you make a new branch, remove "obsolete/gimp-help-2-6-0" to prevent any confusion.