Skip to content

Bump up version to 0.7.0-SNAPSHOT - #1016

Closed
minahlee wants to merge 2 commits into
apache:masterfrom
minahlee:0.7.0-SNAPSHOT
Closed

Bump up version to 0.7.0-SNAPSHOT#1016
minahlee wants to merge 2 commits into
apache:masterfrom
minahlee:0.7.0-SNAPSHOT

Conversation

@minahlee

Copy link
Copy Markdown
Member

What is this PR for?

Bump up version to 0.7.0-SNAPSHOT

@Leemoonsoo

Copy link
Copy Markdown
Member

@minahlee

Copy link
Copy Markdown
MemberAuthor

@Leemoonsoo it's already there

@Leemoonsoo

Copy link
Copy Markdown
Member

Oops i've confused you already took care! thanks!

@Leemoonsoo

Copy link
Copy Markdown
Member

LGTM

@minahlee

Copy link
Copy Markdown
MemberAuthor

no problem!

@darionyaphet

Copy link
Copy Markdown

Have any plan to release 0.6 ?

@bzz

bzz commented Jun 16, 2016

Copy link
Copy Markdown
Member

@minahlee looks great, let's merge it

@darionyaphet all release-related question are discussed on dev@ mailing list and tracked under ZEPPELIN-889

@felixcheung

felixcheung commented Jun 16, 2016

Copy link
Copy Markdown
Member

I don't want to side track this... is it a bit pre-mature to move to 0.7.0 instead of, say, 0.6.1?
And in case I have missed it, what's our plan on versioning/releases?

@Leemoonsoo

Copy link
Copy Markdown
Member

In my understanding, Once 0.6.0 is released from branch-0.6, branch-0.6 will be bumped up to 0.6.1-SNAPSHOT and 0.6.1, 0.6.2 ... will be released from branch-0.6 if necessary.
Meanwhile, master branch becomes 0.7.0-SNAPSHOT.

@minahlee

minahlee commented Jun 16, 2016

Copy link
Copy Markdown
MemberAuthor

@Leemoonsoo Thanks for the explanation!
@felixcheung as @Leemoonsoo said, branch-0.6 will be bumped up to 0.6.1-SNAPSHOT once I create v0.6.0-rc1 tag. We have documented this versioning policy in wiki few months ago. Bug fixes will keep being merged both in master and branch-0.6 and I hope we deliver those maintenance release in one or two month so many users can take advantage of it.

@felixcheung

Copy link
Copy Markdown
Member

ok, thanks for clarification. It's a bit different from our release process (ie. 0.5.5, 0.5.6) before, but I like this better.

@minahlee
minahleeforce-pushed the 0.7.0-SNAPSHOT branch 3 times, most recently from 939ae55 to b5ba3d1CompareJune 25, 2016 07:28
@minahlee

Copy link
Copy Markdown
MemberAuthor

Merging it to publish 0.7.0-SNAPSHOT document as 0.6.0 release vote passed

@jongyoul

Copy link
Copy Markdown
Member

Go for it!!

@Leemoonsoo

Leemoonsoo commented Jul 4, 2016

Copy link
Copy Markdown
Member

LGTM. Actually I think bump up to 0.7.0 could be done right after the branch-0.6 creation.

by the way, #836 has merged. Could you rebase/merge master and take care of following files, too?

zeppelin-examples/pom.xml
zeppelin-examples/zeppelin-example-horizontalbar/pom.xml
zeppelin-examples/zeppelin-example-clock/pom.xml
zeppelin-examples/zeppelin-example-clock/zeppelin-example-clock.json
zeppelin-examples/zeppelin-example-horizontalbar/zeppelin-example-horizontalbar.json

@minahlee
minahleeforce-pushed the 0.7.0-SNAPSHOT branch 10 times, most recently from bdc93d1 to 275bbbeCompareJuly 5, 2016 18:27
@asfgitasfgit closed this in e0f77d6Jul 5, 2016
@minahlee
minahlee deleted the 0.7.0-SNAPSHOT branch August 8, 2016 02:18
PhilippGrulich pushed a commit to SWC-SENSE/zeppelin that referenced this pull request Aug 8, 2016
### What is this PR for?
Bump up version to 0.7.0-SNAPSHOT
Author: Mina Lee <minalee@apache.org>
Closesapache#1016 from minahlee/0.7.0-SNAPSHOT and squashes the following commits:
541e1b3 [Mina Lee] Bump up zeppelin-examples version to 0.7.0-SNAPSHOT
ea8c0ad [Mina Lee] Bump up version to 0.7.0-SNAPSHOT
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

@minahlee@Leemoonsoo@darionyaphet@bzz@felixcheung@jongyoul