my thought would not only be for the bundled extensions but for *everything* under skins/ and extensions/ to get a given REL branch when a release is set. It might mean that some extensions get a REL for a non-compatible branch but it would cover those extensions where devs forget to cut branches.
On Mon, Aug 29, 2016 at 11:25 AM, Chad innocentkiller@gmail.com wrote:
On Mon, Aug 29, 2016 at 8:04 AM John phoenixoverride@gmail.com wrote:
Can we get a repo for each major release that contains core, skins, and
all
extensions in a single checkout? Right now I am updating and with all of the sub modules, I am running into issues where I cant set a branch on
the
extensions/ repo for REL 1_27 and get all extensions as of that
branching,
Instead I am forced to go thru one by one and manually set it, if and
only
if a given extension has said branch set, otherwise I am out of luck.
Getting everything together would cause a larger checkout, but keeps
things
together for those who want to pick and choose.
It's on my todo list to add all the extensions and skins that are bundled in a release to the core release branch as submodules, just haven't gotten around to it yet.
In addition to the problems/benefits you point out, it also means that the extensions and skins would be included in the signed tags for each release, aiding in reproducibility of a release.
-Chad _______________________________________________ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l