05, 2012 4:50 PM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] OpenStack "G" naming poll
Mark Collier wrote:
> That's a good point. I think at this stage just having grizzly on the ballot
> is a fair next step.
Due to limitations in the Launchpad poll system you
Mark Collier wrote:
> That's a good point. I think at this stage just having grizzly on the ballot
> is a fair next step.
Due to limitations in the Launchpad poll system you can't modify (or
cancel) a poll so I had to create a second poll about prefering Grizzly
over anything else that would be
gt; Cc: "openstack@lists.launchpad.net\(openstack@lists.launchpad.net\)"
>> , ThierryCarrez
>> Subject: Re: [Openstack] OpenStack "G" naming poll
>>
>>
>> +1 grizzly
>>
>> On Jul 3, 2012, at 7:45 PM, "Gabriel Hurley"
or thought.
>>
>> - Gabriel
>>
>>
>>
>>
>> From: openstack-bounces+gabriel.hurley=nebula....@lists.launchpad.net
>> [mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net
>> ] On Behalf Of Brian Waldon
>
;openstack@lists.launchpad.net \(openstack@lists.launchpad.net\)"
>, Thierry Carrez
>Subject: Re: [Openstack] OpenStack "G" naming poll
>
>
>+1 grizzly
>
> On Jul 3, 2012, at 7:45 PM, "Gabriel Hurley"
> wrote:
>
>
>
> +1 on “clo
On Wed, Jul 04, 2012 at 10:02:46AM +0200, Thierry Carrez wrote:
> Brian Waldon wrote:
> > On Jul 3, 2012, at 5:21 PM, Monty Taylor wrote:
> >> At the g summit, we'd tell everyone where the next summit is:
> >> At the g summit, we'd vote and announce the name of h
> >> We wouldn't have to spend half
Brian Waldon wrote:
> On Jul 3, 2012, at 5:21 PM, Monty Taylor wrote:
>> At the g summit, we'd tell everyone where the next summit is:
>> At the g summit, we'd vote and announce the name of h
>> We wouldn't have to spend half the cycle saying "h, or whatever" when we
>> mean "we're going to defer t
James E. Blair wrote:
> Brian Waldon writes:
>> TL;DR - Screw the rules, let's call the next release 'Grizzly'
>> [...]
>
> I will join your Bear Flag Revolt.
OK, OK, Jim's flag convinced me, I absolutely need a T-shirt with that.
So I set up a /second/ poll that basically says, ignore the res
Done :-)
Nuage & Co - Razique Mahroua razique.mahr...@gmail.com
Le 4 juil. 2012 à 00:20, Thierry Carrez a écrit :Yes, it's that time of the year again... time for us to choose the nameof the next OpenStack release !This time, cities and counties in California (San Diego, CA being thelocation of th
gt; *From:*
> openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net[mailto:
> openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] *On
> Behalf Of *Brian Waldon
> *Sent:* Tuesday, July 03, 2012 4:50 PM
> *To:* openstack@lists.launchpad.net (openstac
I would like to come out as strongly pro-Grizzly.
I wonder if this release name would make Thierry the "moma grizzly":
http://en.wikipedia.org/wiki/Mama_grizzly
dan
On Wed, Jul 4, 2012 at 1:33 AM, James E. Blair wrote:
> Brian Waldon writes:
>
> > TL;DR - Screw the rules, let's call the next
On 07/03/2012 07:33 PM, James E. Blair wrote:
> Brian Waldon writes:
>
>> TL;DR - Screw the rules, let's call the next release 'Grizzly'
>>
>> As California is rather lacking in the 'municipality names starting
>> with a G that we should use for an OpenStack release' department, I
>> have had t
ces+gabriel.hurley=nebula@lists.launchpad.net>]
On Behalf Of Brian Waldon
Sent: Tuesday, July 03, 2012 4:50 PM
To: openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>
(openstack@lists.launchpad.net<mailto:openstack@lists.launchpad.net>)
Cc: Thierry Carrez
Subject: Re: [
On 07/03/2012 07:29 PM, Brian Waldon wrote:
>
> On Jul 3, 2012, at 5:21 PM, Monty Taylor wrote:
>
>> tl;dr - Screw the rules, I agree
>>
>> Let's at least add it to the poll.
>>
>> Also - I think we should further amend the rules such that we select the
>> NEXT release by the summit for the cur
On Jul 3, 2012, at 5:21 PM, Monty Taylor wrote:
> tl;dr - Screw the rules, I agree
>
> Let's at least add it to the poll.
>
> Also - I think we should further amend the rules such that we select the
> NEXT release by the summit for the current release. That means two things:
>
> At the g summi
tl;dr - Screw the rules, I agree
Let's at least add it to the poll.
Also - I think we should further amend the rules such that we select the
NEXT release by the summit for the current release. That means two things:
At the g summit, we'd tell everyone where the next summit is:
At the g summit, w
ley=nebula@lists.launchpad.net
[mailto:openstack-bounces+gabriel.hurley=nebula@lists.launchpad.net] On
Behalf Of Brian Waldon
Sent: Tuesday, July 03, 2012 4:50 PM
To: openstack@lists.launchpad.net (openstack@lists.launchpad.net)
Cc: Thierry Carrez
Subject: Re: [Openstack] OpenStack "G" naming pol
+1 for Grizzly
On Jul 3, 2012 8:02 PM, "Brian Waldon" wrote:
> TL;DR - Screw the rules, let's call the next release 'Grizzly'
>
> As California is rather lacking in the 'municipality names starting with a
> G that we should use for an OpenStack release' department, I have had to
> look *slightly*
On 07/03/2012 04:50 PM, Brian Waldon wrote:
TL;DR - Screw the rules, let's call the next release 'Grizzly'
Do it!
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~o
TL;DR - Screw the rules, let's call the next release 'Grizzly'
As California is rather lacking in the 'municipality names starting with a G
that we should use for an OpenStack release' department, I have had to look
*slightly* outside the ruleset to find a suitable 'G' release name - that name
Yes, it's that time of the year again... time for us to choose the name
of the next OpenStack release !
This time, cities and counties in California (San Diego, CA being the
location of the G design summit)
I set up a poll with the available options (based on our current rules
of naming) at:
htt
21 matches
Mail list logo
