[dev][tc][all] Train Goal Schedule and Update
Hi all, Since the community goal selection process has taken a turn, we wanted to send an update regarding the current goals. We originally wanted to have the goals for Train be merged by this point to give project teams ample time to plan for them accordingly in their PTG scheduled. Due to discussions raised in each [0][1], it doesn't sound like either will be making it into Train as a feasible community goal. Fortunately, a couple of last minute goals might be a perfect fit for Train, instead of having a release without any community goals. The first one suggested is to render documentation as PDFs [2]. The second goal, which still needs to be proposed, is for IPv6 support. The advantage is that both of these goals are much smaller in scope, but still useful. We're running up against the clock on getting goals selected for Train, but we still have an opportunity to come to agreement on the new proposals before the PTG. We'd like to ask TC and members of the community to review the proposed goals at their earliest convenience. Additionally, if someone wants help write up the IPv6 support goal [3][4], please reach out gmann and mnaser. Even though we were originally trying to make sure we had firm goals well before the PTG, the reduced scope of the new goals should make them easier to talk about in impromptu sessions or the hallway track. Thanks, JP & Lance [0] https://review.openstack.org/#/c/639376/ [1] https://review.openstack.org/#/c/639010/ [2] https://review.openstack.org/#/c/647712/ [3] http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2019-... [4] Note that this goal is for testing IPv6 networking setups in all projects. We already have a tempest full ipv6 job, it would be a matter of making these jobs passing and voting in the future.
On Wed, Apr 03, 2019 at 01:24:29PM -0500, Matt Riedemann wrote:
On 4/3/2019 11:59 AM, Lance Bragstad wrote:
The first one suggested is to render documentation as PDFs [2].
/me waits for mtreinish to propose the same with LaTeX.
Oh, I already commented on the review. It uses LaTeX internally, Sphinx generates LaTeX (and a makefile) and then you compile that into the pdf. The goal is basically to do what I did for Nova 4 years ago [3] (although that has bitrotted quite a bit since then and no longer works) for all projects and add the infrastructure to run and host that as part of docs builds. I wouldn't miss the opportunity to talk LaTeX. :) -Matt Treinish [3] https://github.com/openstack/nova/commit/62575dd40e5b7698d9ba54641558246489f...
Sending a quick follow-up here. We now have a proposal for ipv6 testing support as a community goal [0]. Thanks to gmann for writing it up! I encourage folks to have a look if you have time before the PTG. [0] https://review.openstack.org/653545 On 4/3/19 11:59 AM, Lance Bragstad wrote:
Hi all,
Since the community goal selection process has taken a turn, we wanted to send an update regarding the current goals. We originally wanted to have the goals for Train be merged by this point to give project teams ample time to plan for them accordingly in their PTG scheduled. Due to discussions raised in each [0][1], it doesn't sound like either will be making it into Train as a feasible community goal. Fortunately, a couple of last minute goals might be a perfect fit for Train, instead of having a release without any community goals.
The first one suggested is to render documentation as PDFs [2]. The second goal, which still needs to be proposed, is for IPv6 support. The advantage is that both of these goals are much smaller in scope, but still useful. We're running up against the clock on getting goals selected for Train, but we still have an opportunity to come to agreement on the new proposals before the PTG.
We'd like to ask TC and members of the community to review the proposed goals at their earliest convenience. Additionally, if someone wants help write up the IPv6 support goal [3][4], please reach out gmann and mnaser. Even though we were originally trying to make sure we had firm goals well before the PTG, the reduced scope of the new goals should make them easier to talk about in impromptu sessions or the hallway track.
Thanks,
JP & Lance
[0] https://review.openstack.org/#/c/639376/ [1] https://review.openstack.org/#/c/639010/ [2] https://review.openstack.org/#/c/647712/ [3] http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2019-... [4] Note that this goal is for testing IPv6 networking setups in all projects. We already have a tempest full ipv6 job, it would be a matter of making these jobs passing and voting in the future.
I know ironic has a lot of issues with IPv6, not all of them are even under our control. I quite doubt we can make it, although I know there is downstream interest to make it happen. On 4/17/19 10:15 PM, Lance Bragstad wrote:
Sending a quick follow-up here. We now have a proposal for ipv6 testing support as a community goal [0]. Thanks to gmann for writing it up!
I encourage folks to have a look if you have time before the PTG.
[0] https://review.openstack.org/653545
On 4/3/19 11:59 AM, Lance Bragstad wrote:
Hi all,
Since the community goal selection process has taken a turn, we wanted to send an update regarding the current goals. We originally wanted to have the goals for Train be merged by this point to give project teams ample time to plan for them accordingly in their PTG scheduled. Due to discussions raised in each [0][1], it doesn't sound like either will be making it into Train as a feasible community goal. Fortunately, a couple of last minute goals might be a perfect fit for Train, instead of having a release without any community goals.
The first one suggested is to render documentation as PDFs [2]. The second goal, which still needs to be proposed, is for IPv6 support. The advantage is that both of these goals are much smaller in scope, but still useful. We're running up against the clock on getting goals selected for Train, but we still have an opportunity to come to agreement on the new proposalsbefore the PTG.
We'd like to ask TC and members of the community to review the proposed goals at their earliest convenience. Additionally, if someone wants help write up the IPv6 support goal [3][4], please reach out gmann and mnaser. Even though we were originally trying to make sure we had firm goals well before the PTG, the reduced scope of the new goals should make them easier to talk about in impromptu sessions or the hallway track.
Thanks,
JP & Lance
[0] https://review.openstack.org/#/c/639376/ [1] https://review.openstack.org/#/c/639010/ [2] https://review.openstack.org/#/c/647712/ [3]http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2019-... [4] Note that this goal is for testing IPv6 networking setups in all projects. We already have a tempest full ipv6 job, it would be a matter of making these jobs passing and voting in the future.
Hi all, Updating this thread again with a summary of recent goal selection activity. We have two proposals that are still under review but they seem like feasible goals and have champions. The first is adding the ability generate PDFs of our documentation [0]. The second formally adds IPv6 testing support in the gate for OpenStack services [1]. The authors of both have been diligently responding to feedback, especially under tight time constraints with the PTG fast approaching. There is still an opportunity to weigh-in on each and I encourage you to do so if you haven't already. We're still optimistic that we can merge these goals before the PTG starts next week. Thanks, Lance [0] https://review.opendev.org/#/c/647712/ <https://review.opendev.org/#/c/647712/8> [1] https://review.opendev.org/#/c/653545/ On 4/17/19 3:15 PM, Lance Bragstad wrote:
Sending a quick follow-up here. We now have a proposal for ipv6 testing support as a community goal [0]. Thanks to gmann for writing it up!
I encourage folks to have a look if you have time before the PTG.
[0] https://review.openstack.org/653545
On 4/3/19 11:59 AM, Lance Bragstad wrote:
Hi all,
Since the community goal selection process has taken a turn, we wanted to send an update regarding the current goals. We originally wanted to have the goals for Train be merged by this point to give project teams ample time to plan for them accordingly in their PTG scheduled. Due to discussions raised in each [0][1], it doesn't sound like either will be making it into Train as a feasible community goal. Fortunately, a couple of last minute goals might be a perfect fit for Train, instead of having a release without any community goals.
The first one suggested is to render documentation as PDFs [2]. The second goal, which still needs to be proposed, is for IPv6 support. The advantage is that both of these goals are much smaller in scope, but still useful. We're running up against the clock on getting goals selected for Train, but we still have an opportunity to come to agreement on the new proposals before the PTG.
We'd like to ask TC and members of the community to review the proposed goals at their earliest convenience. Additionally, if someone wants help write up the IPv6 support goal [3][4], please reach out gmann and mnaser. Even though we were originally trying to make sure we had firm goals well before the PTG, the reduced scope of the new goals should make them easier to talk about in impromptu sessions or the hallway track.
Thanks,
JP & Lance
[0] https://review.openstack.org/#/c/639376/ [1] https://review.openstack.org/#/c/639010/ [2] https://review.openstack.org/#/c/647712/ [3] http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2019-... [4] Note that this goal is for testing IPv6 networking setups in all projects. We already have a tempest full ipv6 job, it would be a matter of making these jobs passing and voting in the future.
participants (4)
-
Dmitry Tantsur
-
Lance Bragstad
-
Matt Riedemann
-
Matthew Treinish