I just realized the dates i posted were way out in November - that was an
accident.  I meant October and this week (thursday/friday).  Anyway, not
sure if anyone didn't reply as a result.  I think Daniel/Marko both were
good with this Thursday/Friday when they replied so, as no one else has,
I'm just going to recommend we do this Friday, October 30 at 12pm EST.
I'll post the hangout URL in the dev HipChat room at that time.

Thanks,

Stephen

On Mon, Oct 26, 2015 at 8:38 PM, Marko Rodriguez <[email protected]>
wrote:

> Any time works for me too.
>
> Marko.
>
> http://markorodriguez.com
>
> On Oct 26, 2015, at 3:06 PM, Daniel Kuppitz <[email protected]> wrote:
>
> > Any of the given times would work for me.
> >
> > On Mon, Oct 26, 2015 at 9:35 PM, Stephen Mallette <[email protected]>
> > wrote:
> >
> >> I'm looking at 3.1.0-incubating in JIRA and a large body of work remains
> >> for a 11/16 release date.  As we just introduced a one week code freeze
> >> policy prior to release, that means the end to programming time is
> 11/9.  I
> >> think that this means that in order to make the date, we may need to
> scale
> >> back some of the improvements planned for 3.1.0.
> >>
> >> I'd like to propose that we have an open google hangout to review JIRA
> and
> >> 3.1.0.  Here's some days/times that I'd suggest - if you'd like to join,
> >> please reply with your top 2 best times:
> >>
> >> 11/29 10AM EST
> >> 11/29 11AM EST
> >> 11/29 12PM EST
> >> 11/29 1PM EST
> >> 11/29 2PM EST
> >> 11/30 10AM EST
> >> 11/30 11AM EST
> >> 11/30 12PM EST
> >> 11/30 1PM EST
> >> 11/30 2PM EST
> >>
> >> Hopefully we can converge on a day/time without too much trouble.  afaik
> >> Hangouts will only support 10 connections so if more than 10 want to
> join
> >> we may need to figure something else out, but let's cross that bridge
> when
> >> we come to it.
> >>
> >> I think this will be the first of many open hangouts around release
> >> planning.  Be prepared for some bumps as we try to make this happen for
> the
> >> first time.
> >>
> >> Thanks,
> >>
> >> Stephen
> >>
>
>

Reply via email to