settingsLogin | Registersettings

[openstack-dev] [horizon][release] freeze timelines for horizon in newton

0 votes

In the Trove review of the release schedule this morning, and in the retrospective of the mitaka release process, one question which was raised was the linkage between projects like Trove and Horizon.

This came up in the specific context of the fact that projects like Trove (in the form of the trove-dashboard repository) late in the Mitaka cycle[3]. Late in the Mitaka cycle, a change in Horizon caused Trove to break very close to the feature freeze date.

So the question is whether we can assume that projects like Horizon will freeze in R-6 to ensure that (for example) Trove will freeze in R-5.

Thanks,

-amrith

[1] http://releases.openstack.org/newton/schedule.html
[2] https://review.openstack.org/#/c/311123/
[3] https://review.openstack.org/#/c/307221/


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
asked Apr 29, 2016 in openstack-dev by Amrith_Kumar (10,500 points)   2 4 4

3 Responses

0 votes

This has been discussed (just now) in the release management plan (https://etherpad.openstack.org/p/newton-relmgt-plan) See point 8 under Communication/Governance Changes. From an immediate standpoint, the RC phase of this cycle will be much stricter to prevent late breakages. Going forward, we’re likely going to establish an earlier feature freeze too, pending community discussion.

On a separate note, this email prompted me to scan the governance for the dashboard plugins and it became apparent that several have changed their release tags, without informing Horizon of this release cadence expectation via IRC, email, or our plugin feedback fishbowl. If we are to continue building a good plugin ecosystem, the plugins must communicate their expectations to us upstream; we do not have the time to monitor every plugin.

Rob

On 29 Apr 2016, at 11:26, Amrith Kumar amrith@tesora.com wrote:

In the Trove review of the release schedule this morning, and in the retrospective of the mitaka release process, one question which was raised was the linkage between projects like Trove and Horizon.

This came up in the specific context of the fact that projects like Trove (in the form of the trove-dashboard repository) late in the Mitaka cycle[3]. Late in the Mitaka cycle, a change in Horizon caused Trove to break very close to the feature freeze date.

So the question is whether we can assume that projects like Horizon will freeze in R-6 to ensure that (for example) Trove will freeze in R-5.

Thanks,

-amrith

[1] http://releases.openstack.org/newton/schedule.html
[2] https://review.openstack.org/#/c/311123/
[3] https://review.openstack.org/#/c/307221/


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded Apr 29, 2016 by Rob_Cresswell_(rcres (2,200 points)   3
0 votes

From: Rob Cresswell (rcresswe) [mailto:rcresswe@cisco.com]
Sent: Friday, April 29, 2016 4:28 PM
To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [horizon][release] freeze timelines for horizon in newton

This has been discussed (just now) in the release management plan (https://etherpad.openstack.org/p/newton-relmgt-plan) See point 8 under Communication/Governance Changes. From an immediate standpoint, the RC phase of this cycle will be much stricter to prevent late breakages. Going forward, we’re likely going to establish an earlier feature freeze too, pending community discussion.
[amrith] Thanks Rob, I’ve updated the etherpad with a link to this mail thread.

On a separate note, this email prompted me to scan the governance for the dashboard plugins and it became apparent that several have changed their release tags, without informing Horizon of this release cadence expectation via IRC, email, or our plugin feedback fishbowl. If we are to continue building a good plugin ecosystem, the plugins must communicate their expectations to us upstream; we do not have the time to monitor every plugin.
[amrith] I’m unsure what this expectation is. I tried to google it but came up empty.

I assume that you are asking that we let you know when we release a new version of the dashboard, is that right? Or is it something else? In any event, would you provide me a link to something describing this expectation and I’ll make sure that we try and stay true to it.

Rob

On 29 Apr 2016, at 11:26, Amrith Kumar amrith@tesora.com wrote:

In the Trove review of the release schedule this morning, and in the retrospective of the mitaka release process, one question which was raised was the linkage between projects like Trove and Horizon.

This came up in the specific context of the fact that projects like Trove (in the form of the trove-dashboard repository) late in the Mitaka cycle[3]. Late in the Mitaka cycle, a change in Horizon caused Trove to break very close to the feature freeze date.

So the question is whether we can assume that projects like Horizon will freeze in R-6 to ensure that (for example) Trove will freeze in R-5.

Thanks,

-amrith

[1] http://releases.openstack.org/newton/schedule.html
[2] https://review.openstack.org/#/c/311123/
[3] https://review.openstack.org/#/c/307221/


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 1, 2016 by Amrith_Kumar (10,500 points)   2 4 4
0 votes

Thanks Amrith. I'm referring to the release timeline when I said expectation; previously every plugin had been on an independent release, rather than being the same as Horizon. Several plugins have changed this without any communication; it would've been better to let us know at the time so we could've discussed earlier, or during the summit for example.

Rob

On 1 May 2016 11:26 p.m., "Amrith Kumar" amrith@tesora.com wrote:
From: Rob Cresswell (rcresswe) [mailto:rcresswe@cisco.com]
Sent: Friday, April 29, 2016 4:28 PM
To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [horizon][release] freeze timelines for horizon in newton

This has been discussed (just now) in the release management plan (https://etherpad.openstack.org/p/newton-relmgt-plan) See point 8 under Communication/Governance Changes. From an immediate standpoint, the RC phase of this cycle will be much stricter to prevent late breakages. Going forward, we’re likely going to establish an earlier feature freeze too, pending community discussion.
[amrith] Thanks Rob, I’ve updated the etherpad with a link to this mail thread.

On a separate note, this email prompted me to scan the governance for the dashboard plugins and it became apparent that several have changed their release tags, without informing Horizon of this release cadence expectation via IRC, email, or our plugin feedback fishbowl. If we are to continue building a good plugin ecosystem, the plugins must communicate their expectations to us upstream; we do not have the time to monitor every plugin.
[amrith] I’m unsure what this expectation is. I tried to google it but came up empty.

I assume that you are asking that we let you know when we release a new version of the dashboard, is that right? Or is it something else? In any event, would you provide me a link to something describing this expectation and I’ll make sure that we try and stay true to it.

Rob

On 29 Apr 2016, at 11:26, Amrith Kumar amrith@tesora.com wrote:

In the Trove review of the release schedule this morning, and in the retrospective of the mitaka release process, one question which was raised was the linkage between projects like Trove and Horizon.

This came up in the specific context of the fact that projects like Trove (in the form of the trove-dashboard repository) late in the Mitaka cycle[3]. Late in the Mitaka cycle, a change in Horizon caused Trove to break very close to the feature freeze date.

So the question is whether we can assume that projects like Horizon will freeze in R-6 to ensure that (for example) Trove will freeze in R-5.

Thanks,

-amrith

[1] http://releases.openstack.org/newton/schedule.html
[2] https://review.openstack.org/#/c/311123/
[3] https://review.openstack.org/#/c/307221/


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
responded May 2, 2016 by Rob_Cresswell (2,320 points)   1 2
...