Re: [Wikitech-l] git release branches

2016-08-29 Thread Legoktm
Hi,

On 08/29/2016 10:33 AM, Brad Jorsch (Anomie) wrote:
> On Mon, Aug 29, 2016 at 11:04 AM, John  wrote:
> 
>> 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.
>>
> 
> I see the mediawiki/extensions and mediawiki/skins repos both have a
> REL1_27 branch. Do they somehow not work correctly to check out all
> submodules at the appropriate revisions?

That should work, you'd just need to remember to run "git submodule
update" after switching branches, which should be pretty easy. At that
point you still need to manage 4 different git repos though (core,
vendor, skins, extensions).

-- Legoktm

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] git release branches

2016-08-29 Thread Brad Jorsch (Anomie)
On Mon, Aug 29, 2016 at 11:04 AM, John  wrote:

> 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.
>

I see the mediawiki/extensions and mediawiki/skins repos both have a
REL1_27 branch. Do they somehow not work correctly to check out all
submodules at the appropriate revisions?


-- 
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] git release branches

2016-08-29 Thread Chad
On Mon, Aug 29, 2016 at 8:34 AM John  wrote:

> 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.
>
>
Devs don't have to remember to cut branches, I cut a REL1_* for all
extensions & skins during the release cycle. They aren't retroactively
done for new extensions or skins sure, but they should all be there.

I was talking more about putting the "bundled" ones (ie: those in the
tarballs) as submodules of core release branches like we do for the
wmf/* branches.

-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] git release branches

2016-08-29 Thread John
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  wrote:

> On Mon, Aug 29, 2016 at 8:04 AM John  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
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] git release branches

2016-08-29 Thread Chad
On Mon, Aug 29, 2016 at 8:04 AM John  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

[Wikitech-l] git release branches

2016-08-29 Thread John
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.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l