As you all know, there has recently been several very active discussions
around how to improve assorted aspects of our development process. One idea
that was brought up is to come up with a list of cycle goals/project
priorities for Kilo [0].
To that end, I would like to propose an
On 09/11/2014 07:32 AM, Eoghan Glynn wrote:
As you all know, there has recently been several very active discussions
around how to improve assorted aspects of our development process. One idea
that was brought up is to come up with a list of cycle goals/project
priorities for Kilo [0].
To
On 2014-09-11 01:27:23 -0400 (-0400), Russell Bryant wrote:
[...]
But seriously, we should probably put out a more official notice about
this once Kilo opens up.
It's probably worth carrying in the release notes for all Juno
servers... This is the last release of OpenStack with official
support
-Original Message-
From: Jay Pipes [mailto:jaypi...@gmail.com]
Sent: Tuesday, September 09, 2014 4:29 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Kilo Cycle Goals Exercise
3. Another long-term topic is standardizing our APIs so that we use
consistent
Joe Gordon wrote:
To that end, I would like to propose an exercise as discussed in the TC
meeting yesterday [1]:
Have anyone interested (especially TC members) come up with a list of
what they think the project wide Kilo cycle goals should be and post
them on this thread by end of day
tl;dr I'm concerned we're conflating user concerns and contributor
concerns. I'd like to see laser focus on two things that help both: 1)
Define layers in our governance and integration efforts 2) Pay down
technical debt with a focus on supporting users.
more
Great kick off Joe, thanks. I have
On Wed, Sep 10, 2014 at 7:13 AM, Thierry Carrez thie...@openstack.org wrote:
Joe Gordon wrote:
To that end, I would like to propose an exercise as discussed in the TC
meeting yesterday [1]:
Have anyone interested (especially TC members) come up with a list of
what they think the project wide
On 09/03/2014 11:37 AM, Joe Gordon wrote:
As you all know, there has recently been several very active discussions
around how to improve assorted aspects of our development process. One idea
that was brought up is to come up with a list of cycle goals/project
priorities for Kilo [0].
To
On 09/03/2014 11:37 AM, Joe Gordon wrote:
As you all know, there has recently been several very active discussions
around how to improve assorted aspects of our development process. One idea
that was brought up is to come up with a list of cycle goals/project
priorities for Kilo [0].
To that
So easy/obvious it probably isn't even worth mentioning:
Drop support for python2.6
--
- Gus
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 09/11/2014 12:52 AM, Angus Lees wrote:
So easy/obvious it probably isn't even worth mentioning:
Drop support for python2.6
Yeah, that's been the plan. We discussed this at the Juno summit and
representatives from most (all?) distributions carrying OpenStack were
there. Dropping in Kilo
I haven't had a chance to read other people's posts, so I am sure
there is duplication here.
What would I have all of OpenStack working on if I was ruler of the
universe? Let's see...
1. Fixing our flakey gate: we're all annoyed by our code failing tests
with transient errors, but most people
On Wed, Sep 3, 2014 at 8:37 AM, Joe Gordon joe.gord...@gmail.com wrote:
As you all know, there has recently been several very active discussions
around how to improve assorted aspects of our development process. One idea
that was brought up is to come up with a list of cycle goals/project
Deleting unnecessary code, introducing a stabilization cycle and/or making
definite steps towards a unified SDK are definitely my votes.
*Adam Lawson*
AQORN, Inc.
427 North Tatnall Street
Ste. 58461
Wilmington, Delaware 19801-2230
Toll-free: (844) 4-AQORN-NOW ext. 101
International: +1
On Sun, 7 Sep 2014, Monty Taylor wrote:
1. Caring about end user experience at all
2. Less features, more win
3. Deleting things
Yes. I'll give away all of my list for any one of these.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cdent
On Sep 7, 2014, at 9:27 PM, Anita Kuno ante...@anteaya.info wrote:
On 09/07/2014 09:12 PM, Angus Salkeld wrote:
Lets prevent blogs like this: http://jimhconsulting.com/?p=673 by making
users happy.
I don't understand why you would encourage writers of blog posts you
disagree with by sending
On 09/08/2014 11:12 AM, Mike Bayer wrote:
On Sep 7, 2014, at 9:27 PM, Anita Kuno ante...@anteaya.info wrote:
On 09/07/2014 09:12 PM, Angus Salkeld wrote:
Lets prevent blogs like this: http://jimhconsulting.com/?p=673 by making
users happy.
I don't understand why you would encourage
On Sep 7, 2014, at 8:14 PM, Monty Taylor mord...@inaugust.com wrote:
2. Less features, more win
In a perfect world, I'd argue that we should merge exactly zero new features
in all of kilo, and instead focus on making the ones we have work well. Some
of making the ones we have work
On Sep 8, 2014, at 11:30 AM, Anita Kuno ante...@anteaya.info wrote:
Wow, we are really taking liberties with my question today.
What part of any of my actions current or previous have led you to
believe that I want to now or ever have silenced anyone? I am curious
what led you to believe
On 09/08/2014 12:00 PM, Mike Bayer wrote:
On Sep 8, 2014, at 11:30 AM, Anita Kuno ante...@anteaya.info wrote:
Wow, we are really taking liberties with my question today.
What part of any of my actions current or previous have led you to
believe that I want to now or ever have silenced
@lists.openstack.org,
Date: 09/07/2014 08:15 PM
Subject:Re: [openstack-dev] Kilo Cycle Goals Exercise
On 09/03/2014 08:37 AM, Joe Gordon wrote:
As you all know, there has recently been several very active discussions
around how to improve assorted aspects of our development process. One
idea
Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Kilo Cycle Goals Exercise
Monty,
+1!! I fully agree!! How can I help :-)? Can we dedicate some design summit
sessions to this topic? Ideally, having some stakeholder driven sessions
where we can hear about the user
Amen to this!
I've always felt bad that before yahoo tries to include a new feature in its
openstack cloud/s we have to figure out how much the feature is a land-mine,
how much of it works, how much of it doesn't and so-on. That type of
investigation imho shouldn't really be needed and the
On 09/03/2014 12:16 PM, Doug Hellmann wrote:
On Sep 3, 2014, at 11:37 AM, Joe Gordon joe.gord...@gmail.com
mailto:joe.gord...@gmail.com wrote:
As you all know, there has recently been several very active discussions
around how to improve assorted aspects of our development process. One
idea
On 2014-09-07 8:14 PM, Monty Taylor wrote:
If I were king ...
1. Caring about end user experience at all
If I don't do anything at all next cycle, I will see the above fixed.
Because it's embarrassing. Seriously. Try to use OpenStack from python
some time. I dare you.
[...]
Between 2 and
On Wed, 3 Sep 2014, Joe Gordon wrote:
Have anyone interested (especially TC members) come up with a list of what
they think the project wide Kilo cycle goals should be and post them on
this thread by end of day Wednesday, September 10th. After which time we
can begin discussing the results.
I
Comments in line (added my thoughts on a couple of the targets Sean
outlined).
On Thursday, September 4, 2014, Sean Dague s...@dague.net wrote:
Here is my top 5 list:
1. Functional Testing in Integrated projects
The justification for this is here -
On 09/03/2014 08:37 AM, Joe Gordon wrote:
As you all know, there has recently been several very active discussions
around how to improve assorted aspects of our development process. One idea
that was brought up is to come up with a list of cycle goals/project
priorities for Kilo [0].
To that
Lets prevent blogs like this: http://jimhconsulting.com/?p=673 by making
users happy.
1) Consistent/easy upgrading.
all projects should follow a consistent model to the way they approach
upgrading.
it should actually work.
- REST versioning
- RPC versioning
- db (data)
On 09/07/2014 09:12 PM, Angus Salkeld wrote:
Lets prevent blogs like this: http://jimhconsulting.com/?p=673 by making
users happy.
I don't understand why you would encourage writers of blog posts you
disagree with by sending them traffic.
Anita.
1) Consistent/easy upgrading.
all
On 8 September 2014 13:27, Anita Kuno ante...@anteaya.info wrote:
On 09/07/2014 09:12 PM, Angus Salkeld wrote:
Lets prevent blogs like this: http://jimhconsulting.com/?p=673 by making
users happy.
I don't understand why you would encourage writers of blog posts you
disagree with by sending
On Mon, Sep 8, 2014 at 11:27 AM, Anita Kuno ante...@anteaya.info wrote:
On 09/07/2014 09:12 PM, Angus Salkeld wrote:
Lets prevent blogs like this: http://jimhconsulting.com/?p=673 by making
users happy.
I don't understand why you would encourage writers of blog posts you
disagree with by
On 09/07/2014 09:37 PM, Angus Salkeld wrote:
On Mon, Sep 8, 2014 at 11:27 AM, Anita Kuno ante...@anteaya.info wrote:
On 09/07/2014 09:12 PM, Angus Salkeld wrote:
Lets prevent blogs like this: http://jimhconsulting.com/?p=673 by making
users happy.
I don't understand why you would encourage
On 09/03/2014 11:37 AM, Joe Gordon wrote:
As you all know, there has recently been several very active discussions
around how to improve assorted aspects of our development process. One idea
that was brought up is to come up with a list of cycle goals/project
priorities for Kilo [0].
To
As you all know, there has recently been several very active discussions
around how to improve assorted aspects of our development process. One idea
that was brought up is to come up with a list of cycle goals/project
priorities for Kilo [0].
To that end, I would like to propose an exercise as
On Sep 3, 2014, at 11:37 AM, Joe Gordon joe.gord...@gmail.com wrote:
As you all know, there has recently been several very active discussions
around how to improve assorted aspects of our development process. One idea
that was brought up is to come up with a list of cycle goals/project
36 matches
Mail list logo
