You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@submarine.apache.org by GitBox <gi...@apache.org> on 2020/12/17 22:01:52 UTC

[GitHub] [submarine] pingsutw opened a new pull request #480: Preparing for 0.6.0 development

pingsutw opened a new pull request #480:
URL: https://github.com/apache/submarine/pull/480


   ### What is this PR for?
   Preparing for 0.6.0 development
   
   ### What type of PR is it?
   [Release]
   
   ### Todos
   * [ ] - Task
   
   ### What is the Jira issue?
   * Open an issue on Jira https://issues.apache.org/jira/browse/SUBMARINE/
   * Put link here, and add [SUBMARINE-*Jira number*] in PR title, eg. `SUBMARINE-23. PR title`
   
   ### How should this be tested?
   * First time? Setup Travis CI as described on https://submarine.apache.org/contribution/contributions.html#continuous-integration
   * Strongly recommended: add automated unit tests for any new or changed behavior
   * Outline any manual steps to test the PR here.
   
   ### Screenshots (if appropriate)
   
   ### Questions:
   * Does the licenses files need update? No
   * Is there breaking changes for older versions? No
   * Does this needs documentation? No
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [submarine] asfgit closed pull request #480: Preparing for 0.6.0 development

Posted by GitBox <gi...@apache.org>.
asfgit closed pull request #480:
URL: https://github.com/apache/submarine/pull/480


   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [submarine] tangzhankun edited a comment on pull request #480: Preparing for 0.6.0 development

Posted by GitBox <gi...@apache.org>.
tangzhankun edited a comment on pull request #480:
URL: https://github.com/apache/submarine/pull/480#issuecomment-749301534


   @pingsutw Thanks for the contribution! One question, is it hard for us to update version information besides maven pom.xml? 
   
   Is it possible that we build a script for doing this task? It seems error-prone for one to review this and do manual changes.


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [submarine] pingsutw commented on pull request #480: Preparing for 0.6.0 development

Posted by GitBox <gi...@apache.org>.
pingsutw commented on pull request #480:
URL: https://github.com/apache/submarine/pull/480#issuecomment-750791556


   When updating `pom.xml`, we could use`mvn versions:set -DgenerateBackupPoms=false -DnewVersion=X.(Y+1).Z-SNAPSHOT`, but we need to manual update other files, I can improve it in `0.6.0` 


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [submarine] tangzhankun commented on pull request #480: Preparing for 0.6.0 development

Posted by GitBox <gi...@apache.org>.
tangzhankun commented on pull request #480:
URL: https://github.com/apache/submarine/pull/480#issuecomment-749301534


   @pingsutw Thanks for the contribution! One question, is it hard for us to update version information besides maven pom.xml?


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org