Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Given http://drupal.org/node/991166 and the general push to move translations out of d.o CVS into l.d.o (HURRAY!!!!), I'd like to rip out a ton of complicated code in the packaging script to handle d.o translation project release nodes. Basically, any tarballs that already exist will continue to exist, but no new releases of translation projects would be packaged. In fact, if we haven't already, we should probably alter the release node form to prevent adding new releases of translation projects.
Ripping all this code out would make life easier as I'm working on #781246: Write Git-specific packaging plugin for d.o
In fact, it would have helped a bit with #11416: Please provide *.zip downloads. too...
Thoughts/objections?
Thanks,
-Derek
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 1019354-4.no-translation-packaging.patch | 12.25 KB | dww |
Comments
Comment #1
Gerhard Killesreiter CreditAttribution: Gerhard Killesreiter commentedI generally agree, but would like to see Goba's opinion too.
Comment #2
Gábor HojtsyYes, agreed. And yes, we should modify the release creation form to not allow new translation releases. #980682: Deny creation of new translation projects and releases of existing translations is also waiting to be committed / deployed and #980686: Output a big warning on project/translations and translation projects needs some work to inform actual Drupal users about all this.
Comment #3
dwwGreat, thanks! I replied at #980682 as well...
Comment #4
dwwYay, I love patches to Project* like this. ;)
Comment #5
dwwCommitted to HEAD of project_release and deployed live. Yay!
Comment #6
Gábor HojtsySuperb, superb :) Thank you!