Re: [DISCUSS] Official policy for release maintenance

2017-03-14 Thread Ismaël Mejía
Awesome great to see this explicit. Thanks. On Tue, Mar 14, 2017 at 3:48 PM, Robert Metzger wrote: > I've decided to put it on the download page. Please check out my PR: > https://github.com/apache/flink-web/pull/50 > > On Tue, Mar 14, 2017 at 2:57 PM, Ufuk Celebi wrote: > > > Thanks Robert, I

Re: [DISCUSS] Official policy for release maintenance

2017-03-14 Thread Robert Metzger
I've decided to put it on the download page. Please check out my PR: https://github.com/apache/flink-web/pull/50 On Tue, Mar 14, 2017 at 2:57 PM, Ufuk Celebi wrote: > Thanks Robert, I would like that! > > +1 for adding something to the Downloads page. Maybe add it to the FAQ > and link from the

Re: [DISCUSS] Official policy for release maintenance

2017-03-14 Thread Ufuk Celebi
Thanks Robert, I would like that! +1 for adding something to the Downloads page. Maybe add it to the FAQ and link from the downloads page or the other way around? I don't know what's better. On Tue, Mar 14, 2017 at 2:52 PM, Robert Metzger wrote: > I'll update the Wikipedia article and include t

Re: [DISCUSS] Official policy for release maintenance

2017-03-14 Thread Robert Metzger
I'll update the Wikipedia article and include the details into our wiki. In addition, what do you think about adding the "update guarantees" on the download or FAQ page? On Tue, Mar 14, 2017 at 1:18 PM, Ufuk Celebi wrote: > Hey Ismael, > > thanks for bringing this up. I think it's a very import

Re: [DISCUSS] Official policy for release maintenance

2017-03-14 Thread Ufuk Celebi
Hey Ismael, thanks for bringing this up. I think it's a very important to communicate this on the project web page. On Tue, Mar 14, 2017 at 9:30 AM, Ismaël Mejía wrote: > What do you think guys? Has this been discussed before? Maybe this is a > good moment to decide this, if we haven’t. There w

[DISCUSS] Official policy for release maintenance

2017-03-14 Thread Ismaël Mejía
​Following my previous question at user@ and by Fabian’s suggestion I moved the discussion here. Flink has been growing steadily, and many organizations are asking the question of how are the releases of flink maintained in the long term, so maybe it is a good idea to decide and make public the of