This submitted localization has a lot of contributions to plugins, too. What's the best way to do this? I'm thinking about:
- Create a branch like the one we created for the core in all the affected plugins, committing one locale at a time - Generate a separate set of files that show all the added localizations per locale, across plugins. This is in the hope that people who know the language can easily look across plugins. I suppose another script is needed to eventually merge them, and a mechanism for plugin authors to opt-out (probably by "git merge --ours") 2013/10/28 Kohsuke Kawaguchi <[email protected]> > Thanks! Now that RC for 1.538 is created, I'm merging them into > 1.539-SNAPSHOT. > > > 2013/10/28 Harald Albers <[email protected]> > >> ** >> On 21 Oct 2013 at 10:10, Kohsuke Kawaguchi wrote: >> >> > I really appreciate everyone reviewing the locales they understand. >> > >> > However, the lack of commit access for many means that they'd have to >> > leave comments and I would have to manually apply these changes. >> >> There seemed to come in no more comments, so I incorporated the >> existing ones into a series of commits to the localization-20131020 >> branch. >> >> Regards, >> Harald >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Jenkins Developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > Kohsuke Kawaguchi > -- Kohsuke Kawaguchi -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
