[openstack-dev] [horizon] Weekly wrap-up

[Rob Cresswell]

Hey folks,

Great work since the PTG. In Pike so far we've already closed over 30 bugs (28 
tracked, with a few minor untracked fixes) and backported several fixes to our 
stable releases, which we'll tag this week. Several blueprints are well on the 
way too, but really need reviews. Please check out 
https://launchpad.net/horizon/+milestone/pike-1, and get some +/-1's on those 
patches!

I've been doing a lot of patch cleanup this week; if you believe something has 
been abandoned or blocked erroneously, please let me know via email or IRC 
(robcresswell).

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

[openstack-dev] [Horizon] Weekly wrap-up

[Richard Jones]

Hi folks,

A quiet week this week as folks gear up for Pike and the PTG next week.

We did get Ocata RC2 out the door this week with those final few bug
fixes and the wonderful translations from the i18n team! Thanks to
everyone who helped make Ocata Horizon happen :-)

If you're going to the PTG, or have something you'd like discussed
there, please get your thoughts about Pike planning into the
etherpad[1].


Cheers, and signing off to hand over to Rob for Pike,

Richard

[1] https://etherpad.openstack.org/p/horizon-ptg-pike

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

[openstack-dev] [Horizon] Weekly wrap-up

[Richard Jones]

Hi folks,

We're well on our way to RC2, which will probably be tagged early next
week unless someone objects.We've got the requirements.txt updates for
the xstatic packages in but just need those last couple of domain
context related patches to get in (poke, poke...)

Use domain_context not effective domain to display domains list
  https://review.openstack.org/#/c/427125/
Disentangle domain context from effective domain
  https://review.openstack.org/#/c/427729/

Once those are definitively in or not, we'll know where RC2 stands.

We had a very brief meeting this week thanks in part to being so close
to the end of cycle, but also thanks to my IRC connection being super
flaky. If you have anything you'd like to discuss (or have discussed)
at the PTG, please add it to:

  https://etherpad.openstack.org/p/horizon-ptg-pike


Have a great weekend,

 Richard

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

[openstack-dev] [Horizon] Weekly wrap-up

[Richard Jones]

Hi folks,

The mad rush to RC1 concluded this week with RC1 now tagged and the
stable/ocata branch created. We've got a couple of bugfixes that
should have made the RC1 release but just missed out so we're going to
try to get those in for RC2; otherwise RC1 is a good release, we can
all be happy with it!

This week's meeting covered a few topics beyond the impending RC1 release:

- There was some more talk of the PTG, and sadly a couple of folks
(myself included) won't be making it
- I volunteered to be the new Docs Liaison
- I welcomed our new (and returning) PTL for Pike, Rob Cresswell!


Have a great weekend all,

 Richard

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

[openstack-dev] [Horizon] Weekly wrap-up

[Richard Jones]

Hi folks,

We had a relatively brief Horizon meeting this week[1] in which I
announced the (planned) Feature Freeze that took place this week. This
means that all blueprint-related patches are now put on hold until
after the Ocata release of Horizon is done. In the mean time, only bug
patches and those few patches granted a Feature Freeze Exemption (FFE)
will be merged.

The patches granted FFE should be reviewed with the highest priority
where possible:

Keystone to Keystone Federation Drop Down
  https://review.openstack.org/#/c/408435/
Simple tenant usage pagination
  https://review.openstack.org/#/c/410337/
Add version 2.40 to the supported compute API versions
  https://review.openstack.org/#/c/422642/
Properly compare versions in APIVersionManager
  https://review.openstack.org/#/c/410688/

I will be cutting the milestone 3 release next week; the impact of
that is described on the Ocata release schedule page[2].


 Richard

[1] 
http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-01-18-20.03.html
[2] https://releases.openstack.org/ocata/schedule.html

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

[openstack-dev] [Horizon] Weekly wrap-up

[Richard Jones]

Hi folks,

Welcome back from the break - I hope you had a good one!

We kicked off 2017 with our first weekly meeting[1] that covered a few
areas, notably the impending Ocata feature freeze next week.

We also talked a little about the Pike PTG which is just over a month
away, and I've started a planning etherpad[2] for the sessions we'll
have at the PTG. If you're coming, or would like to have something
discussed at the PTG, please contribute to the etherpad.

I'm at a conference next week so most likely won't make the team
meeting, but it should run anyway. If you have anything to discuss at
the weekly meeting please add it to the agenda[3].

In the mean time, let's get those priority reviews[4] going so we can
get as many landed for Ocata!


 Richard

[1] 
http://eavesdrop.openstack.org/meetings/horizon/2017/horizon.2017-01-11-20.00.html
[2] https://etherpad.openstack.org/p/horizon-ptg-pike
[3] https://wiki.openstack.org/wiki/Meetings/Horizon
[4] https://review.openstack.org/#/q/starredby:r1chardj0n3s%20AND%20status:open

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

Re: [openstack-dev] [Horizon] Weekly wrap-up

[Richard Jones]

Yep, Rob's correct, that's the intent. There's also plenty of non-WIP
high priority patches in the starred list :-)

On 16 December 2016 at 23:31, Rob Cresswell (rcresswe)
 wrote:
> I think the intent is to get eyes on those patches, to prevent a 1000 line
> rewrite only for a core to say “I think this is a bad idea”. So for
> important patches, its probably good to get earlier feedback.
>
> Rob
>
>
> On 16 Dec 2016, at 08:13, Radomir Dopieralski 
> wrote:
>
> I wonder if it really makes sense to put WIP patches on the priority list. I
> think it's a bit counter-productive, considering that the prioritizing of
> patches was supposed to make them merge faster -- but we don't want to merge
> WIP patches, do we?
>
> On Fri, Dec 16, 2016 at 5:31 AM, Richard Jones 
> wrote:
>>
>> Hi folks,
>>
>> No Horizon meeting next week! I'll be around the week after (28th
>> December) so if anyone else is around we can totally have a meeting
>> then.
>>
>> Things that have happened this week, including in the team meeting[1]
>>
>> Ocata-2 was tagged!
>>
>> xstatic-angular-bootstrap 2.2.0.0 was released, which promptly broke
>> Ocata-2 (and Ocata-1, you're welcome). We knew it was coming, and Rob
>> Cresswell had a compatibility patch in place ready to go, so master
>> was back to working within half an hour of the upper-constraints patch
>> enabling 2.2.0.0! If you notice anything busted in Horizon related to
>> bootstrap please file a bug!
>>
>> I'd like to remind everyone that we have a blueprint in play which
>> describes our approach to API microversions[2]. Rob has a patch which
>> will land imminently that implements the core of the design. Please
>> hold off implementing your own version settings/checks! We've seen a
>> few microversion-related patches appear recently, and that's great to
>> see, we just need to make sure we're all heading in the same
>> direction.
>>
>> I've put up the first patch using ui-router which rather dramatically
>> alters the Swift UI[3], so I'd like some feedback on it please.
>>
>> We've got about five(ish) weeks until Feature Freeze[4], folks, so all
>> the help we can get on the priority patches[5] (reviews or coding
>> help) is appreciated!
>>
>>
>> I hope you all get to have some time off, and have an enjoyable holiday,
>>
>>Richard
>>
>> [1]
>> http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-12-14-20.00.html
>> [2] https://blueprints.launchpad.net/horizon/+spec/microversion-support
>> [3] https://review.openstack.org/#/c/350523
>> [4] https://releases.openstack.org/ocata/schedule.html
>> [5]
>> https://review.openstack.org/#/q/starredby:r1chardj0n3s%20AND%20status:open
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: openstack-dev-requ...@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-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Horizon] Weekly wrap-up

[Rob Cresswell (rcresswe)]

I think the intent is to get eyes on those patches, to prevent a 1000 line 
rewrite only for a core to say “I think this is a bad idea”. So for important 
patches, its probably good to get earlier feedback.

Rob


On 16 Dec 2016, at 08:13, Radomir Dopieralski 
> wrote:

I wonder if it really makes sense to put WIP patches on the priority list. I 
think it's a bit counter-productive, considering that the prioritizing of 
patches was supposed to make them merge faster -- but we don't want to merge 
WIP patches, do we?

On Fri, Dec 16, 2016 at 5:31 AM, Richard Jones 
> wrote:
Hi folks,

No Horizon meeting next week! I'll be around the week after (28th
December) so if anyone else is around we can totally have a meeting
then.

Things that have happened this week, including in the team meeting[1]

Ocata-2 was tagged!

xstatic-angular-bootstrap 2.2.0.0 was released, which promptly broke
Ocata-2 (and Ocata-1, you're welcome). We knew it was coming, and Rob
Cresswell had a compatibility patch in place ready to go, so master
was back to working within half an hour of the upper-constraints patch
enabling 2.2.0.0! If you notice anything busted in Horizon related to
bootstrap please file a bug!

I'd like to remind everyone that we have a blueprint in play which
describes our approach to API microversions[2]. Rob has a patch which
will land imminently that implements the core of the design. Please
hold off implementing your own version settings/checks! We've seen a
few microversion-related patches appear recently, and that's great to
see, we just need to make sure we're all heading in the same
direction.

I've put up the first patch using ui-router which rather dramatically
alters the Swift UI[3], so I'd like some feedback on it please.

We've got about five(ish) weeks until Feature Freeze[4], folks, so all
the help we can get on the priority patches[5] (reviews or coding
help) is appreciated!


I hope you all get to have some time off, and have an enjoyable holiday,

   Richard

[1] 
http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-12-14-20.00.html
[2] https://blueprints.launchpad.net/horizon/+spec/microversion-support
[3] https://review.openstack.org/#/c/350523
[4] https://releases.openstack.org/ocata/schedule.html
[5] https://review.openstack.org/#/q/starredby:r1chardj0n3s%20AND%20status:open

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@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-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Horizon] Weekly wrap-up

[Radomir Dopieralski]

I wonder if it really makes sense to put WIP patches on the priority list.
I think it's a bit counter-productive, considering that the prioritizing of
patches was supposed to make them merge faster -- but we don't want to
merge WIP patches, do we?

On Fri, Dec 16, 2016 at 5:31 AM, Richard Jones 
wrote:

> Hi folks,
>
> No Horizon meeting next week! I'll be around the week after (28th
> December) so if anyone else is around we can totally have a meeting
> then.
>
> Things that have happened this week, including in the team meeting[1]
>
> Ocata-2 was tagged!
>
> xstatic-angular-bootstrap 2.2.0.0 was released, which promptly broke
> Ocata-2 (and Ocata-1, you're welcome). We knew it was coming, and Rob
> Cresswell had a compatibility patch in place ready to go, so master
> was back to working within half an hour of the upper-constraints patch
> enabling 2.2.0.0! If you notice anything busted in Horizon related to
> bootstrap please file a bug!
>
> I'd like to remind everyone that we have a blueprint in play which
> describes our approach to API microversions[2]. Rob has a patch which
> will land imminently that implements the core of the design. Please
> hold off implementing your own version settings/checks! We've seen a
> few microversion-related patches appear recently, and that's great to
> see, we just need to make sure we're all heading in the same
> direction.
>
> I've put up the first patch using ui-router which rather dramatically
> alters the Swift UI[3], so I'd like some feedback on it please.
>
> We've got about five(ish) weeks until Feature Freeze[4], folks, so all
> the help we can get on the priority patches[5] (reviews or coding
> help) is appreciated!
>
>
> I hope you all get to have some time off, and have an enjoyable holiday,
>
>Richard
>
> [1] http://eavesdrop.openstack.org/meetings/horizon/2016/
> horizon.2016-12-14-20.00.html
> [2] https://blueprints.launchpad.net/horizon/+spec/microversion-support
> [3] https://review.openstack.org/#/c/350523
> [4] https://releases.openstack.org/ocata/schedule.html
> [5] https://review.openstack.org/#/q/starredby:r1chardj0n3s%
> 20AND%20status:open
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Horizon] Weekly wrap-up

[Richard Jones]

Hi folks,

No Horizon meeting next week! I'll be around the week after (28th
December) so if anyone else is around we can totally have a meeting
then.

Things that have happened this week, including in the team meeting[1]

Ocata-2 was tagged!

xstatic-angular-bootstrap 2.2.0.0 was released, which promptly broke
Ocata-2 (and Ocata-1, you're welcome). We knew it was coming, and Rob
Cresswell had a compatibility patch in place ready to go, so master
was back to working within half an hour of the upper-constraints patch
enabling 2.2.0.0! If you notice anything busted in Horizon related to
bootstrap please file a bug!

I'd like to remind everyone that we have a blueprint in play which
describes our approach to API microversions[2]. Rob has a patch which
will land imminently that implements the core of the design. Please
hold off implementing your own version settings/checks! We've seen a
few microversion-related patches appear recently, and that's great to
see, we just need to make sure we're all heading in the same
direction.

I've put up the first patch using ui-router which rather dramatically
alters the Swift UI[3], so I'd like some feedback on it please.

We've got about five(ish) weeks until Feature Freeze[4], folks, so all
the help we can get on the priority patches[5] (reviews or coding
help) is appreciated!


I hope you all get to have some time off, and have an enjoyable holiday,

   Richard

[1] 
http://eavesdrop.openstack.org/meetings/horizon/2016/horizon.2016-12-14-20.00.html
[2] https://blueprints.launchpad.net/horizon/+spec/microversion-support
[3] https://review.openstack.org/#/c/350523
[4] https://releases.openstack.org/ocata/schedule.html
[5] https://review.openstack.org/#/q/starredby:r1chardj0n3s%20AND%20status:open

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