openstack team mailing list archive

[Paul Voccio <paul.voccio@xxxxxxxxxxxxx>]

Have we considered pruning and expanding the core team to help speed the
reviews along? There are some people who are no longer day-to-day active
in Nova and some that are that could help in this process.

On 2/16/11 3:54 PM, "Soren Hansen" <soren@xxxxxxxxxx> wrote:

>2011/2/16 Jay Pipes <jaypipes@xxxxxxxxx>:
>> Lots of coding and bug fixing has been done in the past weeks. As a
>> result, we've got a big backlog of code reviews to do.
>>
>> If you have some cycles, please do participate:
>>
>> https://code.launchpad.net/nova/+activereviews
>>
>> Nova-core members, remember, it's you responsibility to do code
>>reviews! :)
>
>Yes!
>
>I've considered if nova-core people should take turns in having a review
>day.
>Their top priority for the day should be doing branch reviews and bug
>triaging.  Anything else that day would be second to this.  Every member
>of
>the team should be part of the rotation. The only member of nova-core
>exempt from this responsibility would be Jenkins. :)  f you cannot accept
>this
>responsibility, you don't get to be a member of the team. Of course
>there has to be room for holiday and being ill, but every day, people
>should know who they can bug for reviews and members of the team should
>generally be available for this rotation.
>
>The goal is to ensure that we don't drop good work on the floor due to
>bitrot and to distribute the review load better than we do now.
>
>
>-- 
>Soren Hansen
>Ubuntu Developer    http://www.ubuntu.com/
>OpenStack Developer http://www.openstack.org/
>
>_______________________________________________
>Mailing list: https://launchpad.net/~openstack
>Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>Unsubscribe : https://launchpad.net/~openstack
>More help   : https://help.launchpad.net/ListHelp



Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is prohibited.
If you receive this transmission in error, please notify us immediately by e-mail
at abuse@xxxxxxxxxxxxx, and delete the original message.
Your cooperation is appreciated.