Hey all,
Our release-0.10 branch contains some important fixes (for example a critical fix in the network stack). I would like to hear your opinions about doing a 0.10.2 bug fix release. I think it's a good idea to go for it now. Even though we have the 1.0.0 release coming up, it's not clear when exactly it will be ready to be voted on. Furthermore, I don't expect that everyone will immediately upgrade. Testing a bug fix release is relatively low overhead compared to doing a major release. It should be doable within the week. What's your opinion? If there is a consensus to do it, I would volunteer to be release manager. – Ufuk |
+1 for a 0.10.2 maintenance release.
On Monday, February 1, 2016, Ufuk Celebi <[hidden email]> wrote: > Hey all, > > Our release-0.10 branch contains some important fixes (for example a > critical fix in the network stack). I would like to hear your opinions > about doing a 0.10.2 bug fix release. > > I think it's a good idea to go for it now. Even though we have the 1.0.0 > release coming up, it's not clear when exactly it will be ready to be voted > on. Furthermore, I don't expect that everyone will immediately upgrade. > Testing a bug fix release is relatively low overhead compared to doing a > major release. It should be doable within the week. > > What's your opinion? > > If there is a consensus to do it, I would volunteer to be release manager. > > – Ufuk > |
Hi Ufuk,
+1 If the fixes are straightforward such that we don't need to test extensively, I'm all for it! Releasing doesn't take much time then. On Mon, Feb 1, 2016 at 9:57 PM, Nick Dimiduk <[hidden email]> wrote: > +1 for a 0.10.2 maintenance release. > > On Monday, February 1, 2016, Ufuk Celebi <[hidden email]> wrote: > >> Hey all, >> >> Our release-0.10 branch contains some important fixes (for example a >> critical fix in the network stack). I would like to hear your opinions >> about doing a 0.10.2 bug fix release. >> >> I think it's a good idea to go for it now. Even though we have the 1.0.0 >> release coming up, it's not clear when exactly it will be ready to be voted >> on. Furthermore, I don't expect that everyone will immediately upgrade. >> Testing a bug fix release is relatively low overhead compared to doing a >> major release. It should be doable within the week. >> >> What's your opinion? >> >> If there is a consensus to do it, I would volunteer to be release manager. >> >> – Ufuk >> |
+1
2016-02-02 10:44 GMT+01:00 Maximilian Michels <[hidden email]>: > Hi Ufuk, > > +1 If the fixes are straightforward such that we don't need to test > extensively, I'm all for it! Releasing doesn't take much time then. > > On Mon, Feb 1, 2016 at 9:57 PM, Nick Dimiduk <[hidden email]> wrote: > > +1 for a 0.10.2 maintenance release. > > > > On Monday, February 1, 2016, Ufuk Celebi <[hidden email]> wrote: > > > >> Hey all, > >> > >> Our release-0.10 branch contains some important fixes (for example a > >> critical fix in the network stack). I would like to hear your opinions > >> about doing a 0.10.2 bug fix release. > >> > >> I think it's a good idea to go for it now. Even though we have the 1.0.0 > >> release coming up, it's not clear when exactly it will be ready to be > voted > >> on. Furthermore, I don't expect that everyone will immediately upgrade. > >> Testing a bug fix release is relatively low overhead compared to doing a > >> major release. It should be doable within the week. > >> > >> What's your opinion? > >> > >> If there is a consensus to do it, I would volunteer to be release > manager. > >> > >> – Ufuk > >> > |
+1, since user were asking for it.
On Tue, Feb 2, 2016 at 10:50 AM, Fabian Hueske <[hidden email]> wrote: > +1 > > 2016-02-02 10:44 GMT+01:00 Maximilian Michels <[hidden email]>: > > > Hi Ufuk, > > > > +1 If the fixes are straightforward such that we don't need to test > > extensively, I'm all for it! Releasing doesn't take much time then. > > > > On Mon, Feb 1, 2016 at 9:57 PM, Nick Dimiduk <[hidden email]> wrote: > > > +1 for a 0.10.2 maintenance release. > > > > > > On Monday, February 1, 2016, Ufuk Celebi <[hidden email]> wrote: > > > > > >> Hey all, > > >> > > >> Our release-0.10 branch contains some important fixes (for example a > > >> critical fix in the network stack). I would like to hear your opinions > > >> about doing a 0.10.2 bug fix release. > > >> > > >> I think it's a good idea to go for it now. Even though we have the > 1.0.0 > > >> release coming up, it's not clear when exactly it will be ready to be > > voted > > >> on. Furthermore, I don't expect that everyone will immediately > upgrade. > > >> Testing a bug fix release is relatively low overhead compared to > doing a > > >> major release. It should be doable within the week. > > >> > > >> What's your opinion? > > >> > > >> If there is a consensus to do it, I would volunteer to be release > > manager. > > >> > > >> – Ufuk > > >> > > > |
+1
@Ufuk: Would you be the release manager for that one? On Tue, Feb 2, 2016 at 11:07 AM, Till Rohrmann <[hidden email]> wrote: > +1, since user were asking for it. > > On Tue, Feb 2, 2016 at 10:50 AM, Fabian Hueske <[hidden email]> wrote: > > > +1 > > > > 2016-02-02 10:44 GMT+01:00 Maximilian Michels <[hidden email]>: > > > > > Hi Ufuk, > > > > > > +1 If the fixes are straightforward such that we don't need to test > > > extensively, I'm all for it! Releasing doesn't take much time then. > > > > > > On Mon, Feb 1, 2016 at 9:57 PM, Nick Dimiduk <[hidden email]> > wrote: > > > > +1 for a 0.10.2 maintenance release. > > > > > > > > On Monday, February 1, 2016, Ufuk Celebi <[hidden email]> wrote: > > > > > > > >> Hey all, > > > >> > > > >> Our release-0.10 branch contains some important fixes (for example a > > > >> critical fix in the network stack). I would like to hear your > opinions > > > >> about doing a 0.10.2 bug fix release. > > > >> > > > >> I think it's a good idea to go for it now. Even though we have the > > 1.0.0 > > > >> release coming up, it's not clear when exactly it will be ready to > be > > > voted > > > >> on. Furthermore, I don't expect that everyone will immediately > > upgrade. > > > >> Testing a bug fix release is relatively low overhead compared to > > doing a > > > >> major release. It should be doable within the week. > > > >> > > > >> What's your opinion? > > > >> > > > >> If there is a consensus to do it, I would volunteer to be release > > > manager. > > > >> > > > >> – Ufuk > > > >> > > > > > > |
> On 02 Feb 2016, at 11:43, Stephan Ewen <[hidden email]> wrote: > > +1 > > @Ufuk: Would you be the release manager for that one? Yes. Thanks for the responses so far. I will go ahead and prepare a release candidate soon. If you have any minor fixes, which you would like to have in the release, please report here. – Ufuk |
Thank you for taking care of this. +1
I'd like to include this in to the 0.10.2 release: https://github.com/apache/flink/pull/1576 On Tue, Feb 2, 2016 at 1:57 PM, Ufuk Celebi <[hidden email]> wrote: > > > On 02 Feb 2016, at 11:43, Stephan Ewen <[hidden email]> wrote: > > > > +1 > > > > @Ufuk: Would you be the release manager for that one? > > Yes. > > Thanks for the responses so far. I will go ahead and prepare a release > candidate soon. > > If you have any minor fixes, which you would like to have in the release, > please report here. > > – Ufuk > > |
> On 02 Feb 2016, at 17:30, Robert Metzger <[hidden email]> wrote: > > Thank you for taking care of this. +1 > > I'd like to include this in to the 0.10.2 release: > https://github.com/apache/flink/pull/1576 OK (merged to master and release-10) |
I've created the release candidate and started the vote thread.
This is the document to coordinate testing: https://docs.google.com/document/d/1oCOHwHwZNjHb7MX-qLvA61akEBOAxSIYo53MoygUqxQ/ On Wed, Feb 3, 2016 at 7:31 PM, Ufuk Celebi <[hidden email]> wrote: > > > On 02 Feb 2016, at 17:30, Robert Metzger <[hidden email]> wrote: > > > > Thank you for taking care of this. +1 > > > > I'd like to include this in to the 0.10.2 release: > > https://github.com/apache/flink/pull/1576 > > OK (merged to master and release-10) > > |
Free forum by Nabble | Edit this page |