Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1016
LGTM. Actually I think bump up to 0.6.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
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1016
Merging it to publish 0.7.0-SNAPSHOT document as 0.6.0 release vote passed
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your
Github user felixcheung commented on the issue:
https://github.com/apache/zeppelin/pull/1016
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.
---
If your project is set up for it, you can reply to this
Github user minahlee commented on the issue:
https://github.com/apache/zeppelin/pull/1016
@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
Github user bzz commented on the issue:
https://github.com/apache/zeppelin/pull/1016
@minahlee looks great, let's merge it
@darionyaphet all release-related question are discussed on dev@ mailing
list and tracked under
Github user darionyaphet commented on the issue:
https://github.com/apache/zeppelin/pull/1016
Have any plan to release 0.6 ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user Leemoonsoo commented on the issue:
https://github.com/apache/zeppelin/pull/1016
@minahlee great!
Could you also take care of
https://github.com/apache/zeppelin/blob/master/docs/_config.yml#L24
