Quick follow-up on releases.

The team should currently focus on:

1) https://review.openstack.org/#/q/topic:tripleo/rc1 - features what
we want before tagging rc1.
2) https://launchpad.net/tripleo/+milestone/newton-rc1 bugs
3) https://launchpad.net/tripleo/+milestone/newton-rc2 bugs
4) Upgrade testing (patches will be backported if needed as long as
they are backward compatible)
5) IPv6 testing (patch will be backported if needed)

When 1) is done, I'll tag tripleo rc1 and defer all bugs to newton-rc2.
Another FYI: Puppet OpenStack will release RC1 next week.

Reminder: when rc1 is created, stable/newton branch is also created,
so please take care of backporting your patch merged in master that
you think we need in stable branch.

Thanks everyone, we're almost there! Keep going :-)

On Wed, Sep 14, 2016 at 3:16 PM, Emilien Macchi <emil...@redhat.com> wrote:
> Folks,
> We're currently dealing with multiple CI issues, bug almost all
> blockers are under control.
> Until the release, the whole team should focus on what is targeted here:
> https://launchpad.net/tripleo/+milestone/newton-rc1
> https://launchpad.net/tripleo/+milestone/newton-rc2
> 1) Finish to land patches that are in Newton blueprints: Custom roles,
> Ops tools and Manila/CephFS are the top priorities at this time.
> 2) Work on newton bugs, critical and high. Note: everything that
> concerns Upgrades is critical or high, so it's very important to
> finish this work.
> Because of remaining work, we won't tag RC1 this week but wait the
> week of September 26. That week, we'll tag RC1 and stable/newton will
> be created. Hopefully by this time we solved most of our blockers and
> merged the last patches related to Newton features.
> From there, we'll have to backport bugfixes (and upgrade work) from
> master to stable/newton.
> See more details about release schedule:
> https://releases.openstack.org/newton/schedule.html#n-finalrc
> Any feedback or question is more than welcome,
> --
> Emilien Macchi

Emilien Macchi

OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Reply via email to