Create branches for all specs

[AndyGee]

Each spec that might make it into MP should have a branch

[kenfinnigan]

I'm not sure this is the best approach.

There will be half a dozen or so items that likely fall into this category, and keeping all those branches in sync with master as master changes would be an extremely time consuming maintenance burden.

I would prefer that branches for including specs into the demo are only created once a spec has been agreed to be a part of MicroProfile.

Also from the perspective that how these specs are integrated needs to be correctly architected to ensure the overall project shows off the right things.

[AndyGee]

Those branches would only be there for prototyping and hacking. Once a spec is in, then the branch is out. It's more about accepting PRs away from the master. WDYT?

[kenfinnigan]

I'm not sure what the common view might be, but my thoughts were that we wouldn't be creating branches/including things into the demo app until such time as a specification has been "approved" for inclusion in MicroProfile.

Without this approach, it's very easy for a large number of branches to be present which are for specifications that haven't, and may never, make it into MicroProfile.

I would see any examples or experimentation to show how a specification's implementation works being present within the repo covering the specification, as defined by the Evolution process.

It makes it harder to have a "cohesive" vision for what the demo will be if there's lots of things in flux, as opposed to:

• New specification agreed to be included in MicroProfile
• Architect how best to incorporate that into the demo
• Submit PR with necessary changes