> Patches are here: > http://dcantrel.fedorapeople.org/anaconda/transifex/master/ > > I recommend reading the transifex.txt file as well, which will be added to > the git repo as docs/transifex.txt. I'm okay with the potential slowness of the tx operations. Releases are fairly rare events and the savings of not having an entire group of people outside the team with commit access is a big win as far as I'm concerned. Speaking of which, we'll need to remove transifex from the gitanaconda group. Under the old system, we were able to check that translations were valid before building via the checkbot test. That's moved into autoqa now. Will we have a similar capability under the new transifex system? Do you have to have an account to "tx pull"? Finally, what's the workflow going to be like for the release branches? Do we want to flood them with fXX-alpha-branch, fXX-beta-branch, and so on? Or do those continue to pull from the main fXX-branch? - Chris _______________________________________________ Anaconda-devel-list mailing list Anaconda-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/anaconda-devel-list
