On Fri, Feb 27, 2015 at 4:02 AM, Daniel P. Berrange berra...@redhat.com
wrote:
On Fri, Feb 27, 2015 at 09:51:34AM +1100, Michael Still wrote:
On Fri, Feb 27, 2015 at 9:41 AM, Stefano Maffulli stef...@openstack.org
wrote:
Does it make sense to purge old stuff regularly so we have a better
On Thu, 2015-02-26 at 16:44 -0800, James E. Blair wrote:
It is good to recognize the impact of this, however, I would suggest
that if having open changes that are not actively being worked is a
problem for statistics,
I don't think it's a problem for the statistics per se. The reports are
only
On 02/26/2015 05:41 PM, Stefano Maffulli wrote:
On Thu, 2015-02-26 at 15:58 -0600, Kevin L. Mitchell wrote:
One thing that comes to mind is that there are a lot of reviews that
appear to have been abandoned; I just cleared several from the
novaclient review queue (or commented on them to see
On Fri, Feb 27, 2015 at 09:51:34AM +1100, Michael Still wrote:
On Fri, Feb 27, 2015 at 9:41 AM, Stefano Maffulli stef...@openstack.org
wrote:
Does it make sense to purge old stuff regularly so we have a better
overview? Or maybe we should chart a distribution of age of proposed
On Thu, 2015-02-26 at 15:58 -0600, Kevin L. Mitchell wrote:
One thing that comes to mind is that there are a lot of reviews that
appear to have been abandoned; I just cleared several from the
novaclient review queue (or commented on them to see if they were still
alive). I also know of a few
On Thu, 2015-02-26 at 14:18 -0600, Anne Gentle wrote:
Do the features listed in the Release Notes each have appropriate
documentation? So far we just link to the specifications for nova, for
example. [1] So to me, it could be a focus on the specification
acceptance means less time/energy for
On Wed, 2015-02-25 at 21:15 +, Ian Cordasco wrote:
I read it the same was as Doug. I don’t think Jeremy was trying to
imply your reviews would move through more quickly if you reviewed
other people’s work. Just that, as with most open source projects,
there’s always at least 2 distinct
On Thu, Feb 26, 2015 at 1:45 PM, Stefano Maffulli stef...@openstack.org
wrote:
On Wed, 2015-02-25 at 21:15 +, Ian Cordasco wrote:
I read it the same was as Doug. I don’t think Jeremy was trying to
imply your reviews would move through more quickly if you reviewed
other people’s work.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/26/2015 01:45 PM, Stefano Maffulli wrote:
The interesting bit of those charts is that overall for OpenStack
projects, it seems that the reviews (comments to patchsets) are arriving
quite quickly but the new patchsets take a lot more to be
On Fri, Feb 27, 2015 at 9:41 AM, Stefano Maffulli stef...@openstack.org wrote:
Does it make sense to purge old stuff regularly so we have a better
overview? Or maybe we should chart a distribution of age of proposed
changesets, too in order to get a better understanding of where the
outliers
Stefano Maffulli stef...@openstack.org writes:
On Thu, 2015-02-26 at 15:58 -0600, Kevin L. Mitchell wrote:
One thing that comes to mind is that there are a lot of reviews that
appear to have been abandoned; I just cleared several from the
novaclient review queue (or commented on them to see
On Thu, 2015-02-26 at 11:45 -0800, Stefano Maffulli wrote:
The interesting bit of those charts is that overall for OpenStack
projects, it seems that the reviews (comments to patchsets) are arriving
quite quickly but the new patchsets take a lot more to be submitted.
Too much debating and
On Tue, Feb 24, 2015, Jeremy Stanley fu...@yuggoth.org wrote:
On 2015-02-24 10:00:51 -0800 (-0800), Johannes Erdfelt wrote:
[...]
Recently, I have spent a lot more time waiting on reviews than I
have spent writing the actual code.
That's awesome, assuming what you mean here is that you've
On Wed, Feb 25, 2015, at 12:35 PM, Johannes Erdfelt wrote:
On Tue, Feb 24, 2015, Jeremy Stanley fu...@yuggoth.org wrote:
On 2015-02-24 10:00:51 -0800 (-0800), Johannes Erdfelt wrote:
[...]
Recently, I have spent a lot more time waiting on reviews than I
have spent writing the actual
On 2/25/15, 14:41, Doug Hellmann d...@doughellmann.com wrote:
On Wed, Feb 25, 2015, at 12:35 PM, Johannes Erdfelt wrote:
On Tue, Feb 24, 2015, Jeremy Stanley fu...@yuggoth.org wrote:
On 2015-02-24 10:00:51 -0800 (-0800), Johannes Erdfelt wrote:
[...]
Recently, I have spent a lot more
On Tue, Feb 24, 2015 at 2:38 AM, Thierry Carrez thie...@openstack.org
wrote:
Joe Gordon wrote:
[...]
I think a lot of the frustration with our current cadence comes out of
the big stop everything (development, planning etc.), and stabilize the
release process. Which in turn isn't really
On Tue, Feb 24, 2015 at 2:59 AM, Daniel P. Berrange berra...@redhat.com
wrote:
On Mon, Feb 23, 2015 at 04:14:36PM -0800, Joe Gordon wrote:
Was:
http://lists.openstack.org/pipermail/openstack-dev/2015-February/057578.html
There has been frustration with our current 6 month development
On Tue, Feb 24, 2015 at 10:00 AM, Johannes Erdfelt johan...@erdfelt.com
wrote:
On Tue, Feb 24, 2015, Thierry Carrez thie...@openstack.org wrote:
Agree on the pain of maintaining milestone plans though, which is why I
propose we get rid of most of it in Liberty. That will actually be
On Feb 24, 2015, at 1:50 PM, Joe Gordon joe.gord...@gmail.com wrote:
I think the release candidate
period is the only thing that makes your code drops actually usable.
It's the only moment in the cycle where integrators test. It's the only
moment in the cycle where developers work on bugs
On Mon, Feb 23, 2015 at 04:14:36PM -0800, Joe Gordon wrote:
Was:
http://lists.openstack.org/pipermail/openstack-dev/2015-February/057578.html
There has been frustration with our current 6 month development cadence.
This is an attempt to explain those frustrations and propose a very rough
On Mon, Feb 23, 2015, Joe Gordon joe.gord...@gmail.com wrote:
What this actually means:
- Stop approving blueprints for specific stable releases, instead just
approve them and target them to milestones.
- Milestones stop becoming Kilo-1, Kilo-2, Kilo-3 etc. and just
become
Johannes Erdfelt wrote:
On Mon, Feb 23, 2015, Joe Gordon joe.gord...@gmail.com wrote:
What this actually means:
- Stop approving blueprints for specific stable releases, instead just
approve them and target them to milestones.
- Milestones stop becoming Kilo-1, Kilo-2, Kilo-3
On Tue, Feb 24, 2015, Thierry Carrez thie...@openstack.org wrote:
Agree on the pain of maintaining milestone plans though, which is why I
propose we get rid of most of it in Liberty. That will actually be
discussed at the cross-project meeting today:
On 2015-02-24 10:00:51 -0800 (-0800), Johannes Erdfelt wrote:
[...]
Recently, I have spent a lot more time waiting on reviews than I
have spent writing the actual code.
That's awesome, assuming what you mean here is that you've spent
more time reviewing submitted code than writing more. That's
On 02/24/2015 05:46 PM, Jeremy Stanley wrote:
On 2015-02-24 10:00:51 -0800 (-0800), Johannes Erdfelt wrote:
[...]
Recently, I have spent a lot more time waiting on reviews than I
have spent writing the actual code.
That's awesome, assuming what you mean here is that you've spent
more time
25 matches
Mail list logo
