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
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,
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 effect
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 wi
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 t
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 pl
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
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
mailto:openst...@sheep.art.pl>> 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
wr
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 p
10 matches
Mail list logo
