Bump development version to 0.8.0

[jey]

This patch bumps the version number of the master branch to "0.8.0-SNAPSHOT" so that bugfix releases of the 0.7.x branch can be made, and to comply with the Semantic Versioning convention.

[pwendell]

Thanks for catching this - I think maybe it was just a typo when Matei
bumped versions to 0.7.1 in the master branch. If you look at the last
major release, we bumped the master version to

0.7.0-SNAPSHOT

Just after we cut 0.6.0

0967e71

On Mon, Apr 1, 2013 at 9:07 AM, Jey Kottalam notifications@github.com wrote:

This patch bumps the version number of the master branch to "0.8.0-SNAPSHOT"
so that bugfix releases of the 0.7.x branch can be made, and to comply with
the Semantic Versioning convention.

---

You can merge this Pull Request by running

git pull https://github.com/jey/spark bump-development-version-to-0.8.0

Or view, comment on, or merge it at:

#549

Commit Summary

Bump development version to 0.8.0

File Changes

M bagel/pom.xml (2)
M core/pom.xml (2)
M docs/_config.yml (4)
M examples/pom.xml (2)
M pom.xml (2)
M project/SparkBuild.scala (2)
M repl-bin/pom.xml (2)
M repl/pom.xml (2)
M repl/src/main/scala/spark/repl/SparkILoop.scala (2)
M streaming/pom.xml (2)

Patch Links:

https://github.com/mesos/spark/pull/549.patch
https://github.com/mesos/spark/pull/549.diff

[mateiz]

As discussed on the mailing list, I don't think we need to do this yet. Eventually we will need to create a branch-0.7 which contains fixes to 0.7.x and change master to 0.8, but right now the fixes in master are also good for 0.7.1.

[markhamstra]

My only problem with your approach, Matei, is with new functionality added to 0.7.1-SNAPSHOT leaking out into an eventual 0.7.1 release before it is fully mature. For example, in catching up with #456, it strikes me that there is enough overlap with the recently merged #510 (mapWith, filterWith, etc.) that I'll likely do a refactoring/combining/extending of these efforts later this week. That's fine as long as there haven't been any severe bugs requiring a 0.7.1 release yet, but we probably should try to segregate new API functionality from purely bugfix changes so that a bugfix release can easily be made without leaking new public API that we may still want to rework.

[AmplabJenkins]

Can one of the admins verify this patch?

[massie]

Jenkins, test this please.

[AmplabJenkins]

Merged build triggered.

[AmplabJenkins]

Merged build started.

[AmplabJenkins]

Merged build finished.

[mateiz]

I've merged this in and created a branch-0.7 for further development of 0.7. Thanks Jey!