After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 647992 - GNOME 3.0 string set
GNOME 3.0 string set
Status: RESOLVED NOTABUG
Product: website
Classification: Infrastructure
Component: l10n.gnome.org
current
Other All
: Normal normal
: ---
Assigned To: Website l10n-status maintainers
Website l10n-status maintainers
: 647993 647994 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2011-04-17 02:53 UTC by Chris Leonard
Modified: 2011-05-23 22:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Chris Leonard 2011-04-17 02:53:54 UTC 
The GNOME 3.0 string set has not been forked and frozen in Damned Lies Localization server.

http://l10n.gnome.org/module/gnome-desktop/
Comment 1 Claude Paroz 2011-04-20 15:00:44 UTC 
Hi Chris,
I'm not sure what you are asking here. gnome-desktop has no gnome-3-0 branch yet, so the master branch should be considered for GNOME 3 translations.
It might be easier to discuss this on #i18n IRC channel for further details.

Reopen if I misunderstood you.
Comment 2 Chris Leonard 2011-04-21 18:09:54 UTC 
It's pretty simple.  I understand GNOME 3.0 to be stable and string frozen,  GNOME desktop has a history of branching each release in the past, so it can be expected to branch for 3.0 at some point (probably soonish as many other modules have already branched).  I am trying to provide stable links to downstream L10n effort that needs these strings in it's builds, so I need to track when it does branch. I do not require immediate action, but the closure of this ticket will notify me that the branch has occurred allowing me to adjust my documentation.
Comment 3 Claude Paroz 2011-04-21 18:39:33 UTC 
If not already the case, I suggest you subscribe to gnome-i18n@gnome.org mailing list, because branch notifications are automatically published on the list.
Comment 4 Vincent Untz 2011-04-26 07:12:14 UTC 
*** Bug 647994 has been marked as a duplicate of this bug. ***
Comment 5 Vincent Untz 2011-05-23 22:16:07 UTC 
*** Bug 647993 has been marked as a duplicate of this bug. ***