2018-04-23 17:18:26 UTC - Sijie Guo: @Jai Asher how are we going to do 1.22.1? 
cherry-pick and push a PR and update #1631?
----
2018-04-23 17:32:06 UTC - Matteo Merli: I’d say we don’t need to code review 
again since the changes were already reviewed. 

We could get started by going through the list of bugs fixed in current master 
<https://github.com/apache/incubator-pulsar/issues?page=1&amp;q=milestone%3A2.0.0-incubating+label%3Atype%2Fbug+is%3Aclosed>
 and see what applies. 

Again, I think the easiest way would be to just stack the issues/prs in a 
github project. 

@Jai Asher, regarding the branch, 1.22.1 would be the tag, but the convention 
we have adopted always was to use `branch-1.22` as the branch name, and then 
`v1.22.1-incubating` as the tag
----
2018-04-23 17:55:12 UTC - Jai Asher: ok I will delete `1.22.1` branch
----
2018-04-23 17:58:32 UTC - Jai Asher: Also have created a project as per @Matteo 
Merli suggestion
----
2018-04-23 17:58:33 UTC - Jai Asher: 
<https://github.com/apache/incubator-pulsar/projects>
----
2018-04-23 17:59:30 UTC - Matteo Merli: thanks, added columns
----
2018-04-23 23:58:39 UTC - Matteo Merli: @Jai Asher I have added few commits as 
proposed to backport. Can you go through the list as well? Also, please send a 
message to dev@ list to have more people to add fixes to be backport to 1.22.1
+1 : Jai Asher
----
2018-04-24 00:43:16 UTC - Sijie Guo: @Rajan Dhabalia - here is the PR : 
<https://github.com/apache/incubator-pulsar/pull/1636>
----
2018-04-24 01:26:43 UTC - Rajan Dhabalia: :+1:
----
2018-04-24 01:31:55 UTC - Rajan Dhabalia: @Matteo Merli @Sijie Guo I think we 
can avoid control-topic approach in replicator framework and we can try to make 
it more generic if pulsar-function provides a way to control function state(eg: 
start/stop).. you can add your feedback and views on 
<https://github.com/apache/incubator-pulsar/issues/1582> and we can quickly 
address it
----

Reply via email to