github repository split

[Auntie Mangos]

Greetings,

since we currently do have three different branches of mangos, namely mangos-zero for vanilla WoW, mangos-0.12 for the Burning Crusade expansion, and the master branch for WotLK.

Yehonal from mangos-zero has suggested splitting each branch into one repository of its own.

I'd like to hear your opinions on that.

[VladimirMangos]

I also discuss this with Yehonal and also remember original suggestion from freghar.

freghar mian point that i also agree: mangos-0.12 branched long time ago and all tail have different git commit hashs, so just not help in share data in repo. For mangos master or mangos-0.12 users will be improvment not need download at original repo checkout unrelated branch data. For mangos devs interesting in 0.12 development help for example by backporting own commits don't must be problem just add local branch linked with new repo instead branch in master repo.

Just for clarify: you suggest create for mangos-0.12 repo under mangos organization account as main repo placed.

Maybe this also let re-host back mangoszero to mangos organization account...

[Auntie Mangos]

My suggestion would actually be:

- the current mangos repository should become a place for 4.0.x development.

- add three new repositories: one for vanilla, BC, and WotLK.

Thus: mangos/mangos always is current WoW version.

[DasBlub]

splitting up the repos could also be useful to give some users only commit access to some of those branches (e.g. someone only working on 0.12 but not on master).

i'd go for mangos/mangos-vanilla (= mangos zero), mangos/mangos-tbc (= mangos-0.12), mangos/mangos-wotlk (=mangos master) and mangos/mangos-cata (mangos 4.x)

[VladimirMangos]

- the current mangos repository should become a place for 4.0.x development.

Making master as 4.x related just will create porblems and confussion. I think current state in this part fine: we have 400 branch

until it will be playable at some acceptable level. It just useless made master 4.x related when most devs who not work at low level connectivity staff as me for example can't use client with it. So just move mangos-0.12 branch to new repo i think only need for current repo state.

[Auntie Mangos]

I have added a repository for mangos-zero here: https://github.com/mangos/zero.

I also added a repository for the 0.12 branch here: https://github.com/mangos/one.

I have not used any expansion names but simply expansion numbers (avoiding trademarked names).

Update

mangos-zero repository is populated, the mangos-0.12 branch has been moved into its own repository, too.

[Auntie Mangos]

Forgot to mention: I have added commit groups for each repository, thus those who want to work on multiple repositories, raise a hand and tell me which ones, or message TheLuda on github.

[DasBlub]

will you post an information somewhere, so that the users know about the new repos? at least at a short sight, i haven't seen any information.

oh, and... *raises his hand* ...I'd like to have commit-access to mangos/one

[TheLuda]

Of course. Both

[VladimirMangos]

I update project names in code for MaNGOS One (from mangos-0.12) and MaNGOS Zero (from MaNGOSZero)

and in same time test repost commit access. All look like working

[DasBlub]

hm... why haven't you also moved the '400' branch into an own repo? something like mangos/future_versions or so? maybe a repo without a 'master' branch but only with branches like '400', '403a', etc.

[VladimirMangos]

In different from old forked branches for diff cleitn versions like Zero/One no reson do same for 400.

It more easy merge and cherry-pick commits when master and 400 in same repo. Ofc, maybe TOM can comment this because he more often do it. Independent repo for me for something stable that will continue exist not limited time.

About permissions to new repos, maybe more easy just grand all mangos team access to at least mangos one?

And maybe to mangos zero (if Yehonal no have objection for this part). Maybe not many devs really interesting Zero/one development but we i think can be sure ( ^.^ ) that mangos team devs will not do wrong things if we trusted to commit to master repo

[Auntie Mangos]

ofc done