Re: [DISCUSS] Managing announcements of breaking API / state compatibility changes in major releases

2017-07-16 Thread Tzu-Li (Gordon) Tai
: [DISCUSS] Managing announcements of breaking API / state   compatibility changes in major releases +1 This sounds very good! I just hope that everyone is aware enough and doesn’t forget adding these tags. > On 6. Jul 2017, at 09:59, Tzu-Li (Gordon) Tai wrote: > > > Hi devs, > &g

Re: [DISCUSS] Managing announcements of breaking API / state compatibility changes in major releases

2017-07-06 Thread Tzu-Li (Gordon) Tai
.  Original message From: Aljoscha Krettek Date: 7/6/17 2:01 AM (GMT-08:00) To: dev@flink.apache.org Subject: Re: [DISCUSS] Managing announcements of breaking API / state   compatibility changes in major releases +1 This sounds very good! I just hope that everyone is aware enough

Re: [DISCUSS] Managing announcements of breaking API / state compatibility changes in major releases

2017-07-06 Thread Ted Yu
breaking API / state   compatibility changes in major releases +1 This sounds very good! I just hope that everyone is aware enough and doesn’t forget adding these tags. > On 6. Jul 2017, at 09:59, Tzu-Li (Gordon) Tai wrote: > > > Hi devs, > > I would like to follow up my proposa

Re: [DISCUSS] Managing announcements of breaking API / state compatibility changes in major releases

2017-07-06 Thread Aljoscha Krettek
+1 This sounds very good! I just hope that everyone is aware enough and doesn’t forget adding these tags. > On 6. Jul 2017, at 09:59, Tzu-Li (Gordon) Tai wrote: > > > Hi devs, > > I would like to follow up my proposal in [1] regarding how we can more > systematically and easily collect brea