On Wed, Oct 26, 2011 at 4:09 AM, Kévin Raymond <[email protected]>wrote:
> > Great thanks Sijis, > Currently, translations are like the following: > - spins is building in f16-beta, pulling translations from > fedora-web.spins-fedoraproject-org > - spins staging is (or is going to) building from master pulling > translations from fedora-web.spins-fedoraproject-org > - fpo is building in f16-beta, pulling translations from > fedora-web.fedoraproject-org-f16-beta > - fpo staging is building in master, pulling translations from > fedora-web.fedoraproject-org-f16-beta > > Wouldn't it be a clever change to pull staging translations from > master, and create a fedora-web.spins-fedoraproject-org-f16-beta > resource under transifex in order to keep the current one > translatable? > I would also propose to pull the fpo staging translations from master > (fedora-web.fedoraproject-org). > If you agree, tell me and I'll make necessary .tx/config changes and > merge current translations. Also setting the Importance flag in TXN > would be great. I am also going to write to the translators mailing > list. > > -- > Kévin Raymond > User:shaiton > GPG-Key: A5BCB3A2 > In short answer yes. I haven't done any of the cleanup after the merge. In theory every branch (eg f16-alpha, f16-beta, etc) should have its own resource in tx for each respective site (fp.o, spins.fp.o, etc). I keep overlooking that step and that's why its all messed up until a few weeks ago when you and nb did some cleanup. If possible, could you add a section to the Websites Release SOP [1] so we have something to refer on what's needing update for a release. Staging should pull from the master tx resource. I think your ideas are great. Sijis [1] - http://fedoraproject.org/wiki/Fedora_Websites_Release_SOP
-- websites mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/websites
