Community
Participate
Working Groups
Right now an Eclipse commiter has to submit a given release into Babel so that the translation begins. The operation itself is not hard or time consuming, but we tend to forget about it. Now that the PMI (project management infrastructure) offers a consolidated view of the data linked to a given release (version, and URI of some repository) wouldn't it be great to directly use this information and automatically/regularly submit new releases on Babel ? (Let's say through some cron job or something ?) Furthermore, if Babel is able to handle re-submissions of a given release, it would enable to start working on translations even on milestones builds. What do you think ?
This is my yearly ping ;) I think Babel is great but largely under-used because it requires a specific involvement from the projects. Another stupid question : would that be realistic to submit the whole release train (and the corresponding milestones ?) just using the p2 repository as an input ?
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
