Better repos organisation

[julien-f]

Merging xo/xo-web/xo-server

Pros:

• only one repo from where to manage issues
• XO-Web & XO-Server are developed synchronously and the adding of a feature often requires to create branches and pull requests in each of these repos, having a single repo will be easier

Related discussions:

• Babel reasoning

Set default branch as the default branch

• Rename master to stable
• Rename next-release as master
• Set master as the default branch

Pros:

• no more erroneous pull requests against the stable branch

Cons:

• people using XO from sources might accidentally use the the dev version but this should not be a big problem due to our new work process (the dev branch is always usable)

[olivierlambert]

1/ Fully agree for the default branch stuff (github flow)
2/ Only questions about consistency by merging xo-web and xo-server, without the other modules/plugins.

[olivierlambert]

@julien-f so xo-web will be renamed? Is it possible? If not, what about all the existing/previous issues and milestones?

edit: renaming seems OK. xen-orchestra for the future name?

[julien-f]

xen-orchestra looks fine to me.

[olivierlambert]

Me too. What about merging after the next release?

[olivierlambert]

@julien-f would you consider to merge also xo repo with xo-server and xo-web?

Which name this "super repo" should have? xen-orchestra?

We need to discuss the impact for XOAs too (tomorrow?)

[julien-f]

This is currently blocked due to xoa-packager.