Rationalise and rename branches

[dwijnand]

We should rationalise and rename our repo branches.

Current we have:

• sbt/sbt#0.13
• Jetty webdefault.xml #1.0.x
• Generate datatypes with sat-datatype, fix dependencies between projects zinc#1.0
• Update to sbt/io v1.0.0-M1, cross build, setup Travis librarymanagement#1.0
• Setup travis, public tests in utilLogging util#1.0

@eed3si9n do we need to just rename sbt/sbt's 1.0.x branch to 1.0?

On a very related note, when are we allowing binary breaking changes?

• 1.1, aka Scala SemVer, or
• 2.0, aka Semver / Java SemVer

And is the answer different between sbt/sbt and the sbt modules?

[eed3si9n]

I think we should try to keep (mostly) bincompat during 1.x.y aka Java SemVer across all modules.

[dwijnand]

1. Does it not make sense to rename all the branches 1.x then? (The alternative name "1" is too common to be useful)

2. What do you mean by "(mostly)" keep bincompat?

[jvican]

Java SemVer (normal semantic versioning) is the way to go IMO.

[dwijnand]

Done! All repos are now 1.x.