On Mon, Dec 09, 2013 at 01:16:37PM -0800, Steve Beattie wrote: > changes from there back in to trunk, especially since it looks like > Christian and Kshitij are contributing translations via launchpad :).
Yay! > I currently have the launchpad integration committing changes > automatically to the bzr branch > > > https://code.launchpad.net/~apparmor-dev/apparmor/launchpad-translations-branch > > (I didn't want to let it automatically commit to trunk.) Yay! > In particular, the initial changes launchpad made in rewriting back > the .po files are are rather large. Attempting to review these via > the list I think would be unwieldy at best. Agreed, I wouldn't have fun with that review anyway. > I'd like to have the group's consensus that changes made via launchpad > should be treated as a patch submission, and that a reviewer with > commit access should be able to merge these changes to trunk, without > needing to go to the list (obviously, the list is available should > specific questions arise). And of course, it would be on the person > doing the merge to review the changes to confirm that they're sane, > to the extant possible without having knowledge of the languages > in question. > > I ask, because translations people have made fixes and I would like > to get them incorporated into trunk, and so I want to move on getting > the two trees in sync. > > Are people okay with this? Is there another way we should handle this? This sounds great. Faster iteration on translations is probably key to getting better translation coverage overall. Thanks
signature.asc
Description: Digital signature
-- AppArmor mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/apparmor
