You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by GitBox <gi...@apache.org> on 2020/09/08 06:43:39 UTC

[GitHub] [incubator-dolphinscheduler] CalvinKirs edited a comment on issue #3641: [VOTE]next version what to do

CalvinKirs edited a comment on issue #3641:
URL: https://github.com/apache/incubator-dolphinscheduler/issues/3641#issuecomment-688595898


   1:Api Server communicate for Master instand of scan command table( @qiaozhanwei )
   
   2:Alert module support service for other service invoke( @qiaozhanwei @gaojun2048 )
   
   3:SQL task support multiple sqls and parameter passing optimization(we should add a new task type, such as SqlScript @gabrywu @qiaozhanwei @yangyichao-mango )[need discuss]
   
   4:Support passing parameters between tasks ( @qiaozhanwei )
   
   5:Sort out and simplify the license process
   
   6:Focus on fixing bugs base on the branch some new features can be released in 1.4.0_release base on branch 'dev'.(@gabrywu )
   
   8:SPI requirements are collected and developed. We need to have a discussion to find out the modules that currently need SPI most( @gaojun2048 @lenboo @CalvinKirs )
   
   10:state machine processor of worker and master optimize( @yangyichao-mango )
   
   11:How to do project migration.Including workflow definitions, resource files, and data sources.The development environment and the production environment are two sets of environments.(@BoYiZhang)
   
   12:Adding a batch stop on the process instance page(@xingchun-chen )
   
   13:Many new functions have been added in the dev branch and some issues have been solved. It is recommended to merge them into the next version(@ALL)
   
   Voting email address:https://lists.apache.org/thread.html/r931baa57099e6ddd639d1b8c7a33c3e3b8d03352fb0de82b45a7dfb3%40%3Cdev.dolphinscheduler.apache.org%3E
   
   


----------------------------------------------------------------
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