Re: [DISCUSS] Official policy for release maintenance
Awesome great to see this explicit. Thanks. On Tue, Mar 14, 2017 at 3:48 PM, Robert Metzgerwrote: > 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 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 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 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 was a discussion [1] about adopting time based releases were > > >> most committers and contributors agreed to support the last two major > > >> versions, e.g. the latest stable and the previous stable (1.2 and 1.1 > > >> for our current release). > > >> > > >> It would be nice to formulate this officially somewhere with more > > >> details, e.g. previous major release gets critical bug fixes only. The > > >> time based releases Wiki page [2] does not do this currently. > > >> > > >> Is that in line with the Wikipedia article? It could be that the > > >> wording was/is confusing. > > >> > > >> [1] http://apache-flink-mailing-list-archive.1008284.n3. > > >> nabble.com/DISCUSS-Time-based-releases-in-Flink-td15386.html > > >> > > >> [2] https://cwiki.apache.org/confluence/display/FLINK/Time- > > based+releases > > >> > > >
Re: [DISCUSS] Official policy for release maintenance
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 Celebiwrote: > 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 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 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 was a discussion [1] about adopting time based releases were > >> most committers and contributors agreed to support the last two major > >> versions, e.g. the latest stable and the previous stable (1.2 and 1.1 > >> for our current release). > >> > >> It would be nice to formulate this officially somewhere with more > >> details, e.g. previous major release gets critical bug fixes only. The > >> time based releases Wiki page [2] does not do this currently. > >> > >> Is that in line with the Wikipedia article? It could be that the > >> wording was/is confusing. > >> > >> [1] http://apache-flink-mailing-list-archive.1008284.n3. > >> nabble.com/DISCUSS-Time-based-releases-in-Flink-td15386.html > >> > >> [2] https://cwiki.apache.org/confluence/display/FLINK/Time- > based+releases > >> >
Re: [DISCUSS] Official policy for release maintenance
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 Metzgerwrote: > 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 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 was a discussion [1] about adopting time based releases were >> most committers and contributors agreed to support the last two major >> versions, e.g. the latest stable and the previous stable (1.2 and 1.1 >> for our current release). >> >> It would be nice to formulate this officially somewhere with more >> details, e.g. previous major release gets critical bug fixes only. The >> time based releases Wiki page [2] does not do this currently. >> >> Is that in line with the Wikipedia article? It could be that the >> wording was/is confusing. >> >> [1] http://apache-flink-mailing-list-archive.1008284.n3. >> nabble.com/DISCUSS-Time-based-releases-in-Flink-td15386.html >> >> [2] https://cwiki.apache.org/confluence/display/FLINK/Time-based+releases >>
Re: [DISCUSS] Official policy for release maintenance
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 Celebiwrote: > 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 was a discussion [1] about adopting time based releases were > most committers and contributors agreed to support the last two major > versions, e.g. the latest stable and the previous stable (1.2 and 1.1 > for our current release). > > It would be nice to formulate this officially somewhere with more > details, e.g. previous major release gets critical bug fixes only. The > time based releases Wiki page [2] does not do this currently. > > Is that in line with the Wikipedia article? It could be that the > wording was/is confusing. > > [1] http://apache-flink-mailing-list-archive.1008284.n3. > nabble.com/DISCUSS-Time-based-releases-in-Flink-td15386.html > > [2] https://cwiki.apache.org/confluence/display/FLINK/Time-based+releases >
Re: [DISCUSS] Official policy for release maintenance
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íawrote: > What do you think guys? Has this been discussed before? Maybe this is a > good moment to decide this, if we haven’t. There was a discussion [1] about adopting time based releases were most committers and contributors agreed to support the last two major versions, e.g. the latest stable and the previous stable (1.2 and 1.1 for our current release). It would be nice to formulate this officially somewhere with more details, e.g. previous major release gets critical bug fixes only. The time based releases Wiki page [2] does not do this currently. Is that in line with the Wikipedia article? It could be that the wording was/is confusing. [1] http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-Time-based-releases-in-Flink-td15386.html [2] https://cwiki.apache.org/confluence/display/FLINK/Time-based+releases