On Tue, Jan 27, 2015 at 04:27:21AM +, Adrian Otto wrote:
> Tony,
>
> That would be terrific. Which iCal feed were you thinking of? I was planning
> on making something similar to this:
Sorry Adrian I was a little off topic.
I was thinking that when you settle on a schedule for your regular
Tony,
That would be terrific. Which iCal feed were you thinking of? I was planning on
making something similar to this:
https://wiki.openstack.org/wiki/Kilo_Release_Schedule
But under Magnum on the wiki. Were you thinking I would proceed with that plan,
or would it be more appropriate to put a
On Fri, Jan 23, 2015 at 03:14:18PM -0700, Steven Dake wrote:
> On 01/23/2015 02:46 PM, Adrian Otto wrote:
> >Steven,
> >
> >Thanks for this email to capture and relay this decision from our IRC team
> >meeting this week! I thought it might be helpful if I made a team calendar
> >with an iCal feed t
On 01/23/2015 02:46 PM, Adrian Otto wrote:
Steven,
Thanks for this email to capture and relay this decision from our IRC team
meeting this week! I thought it might be helpful if I made a team calendar with
an iCal feed that our team can subscribe to that would include our team meeting
schedul
Steven,
Thanks for this email to capture and relay this decision from our IRC team
meeting this week! I thought it might be helpful if I made a team calendar with
an iCal feed that our team can subscribe to that would include our team meeting
schedule, and our milestones to help make our plans
TLDR; moving Magnum to match upstream release scheduling intersecting k3
As discussed in our last IRC meeting we want to merge our Magnum
milestone schedules with the upstream OpenStack schedules as soon as
feasible. We think it is feasible to merge release schedules for K3.
As such, We have