Hi folks,

I spoke with ttx, and we decided to merge the following bug as part of G-3,
since it is required to test pagination + xml:
https://review.openstack.org/#/c/21410/

I reviewed it and gave it a +1, but I'd like at least one other person more
familiar with the xml API code to review it.  Thanks,

Dan


On Wed, Feb 20, 2013 at 2:46 AM, Gary Kotton <gkot...@redhat.com> wrote:

>  Hi,
> It looks like things have improved. I think that the real test is when the
> guys in the US start working.
> Thanks
> Gary
>
>
> On 02/20/2013 01:14 AM, Dan Wendlandt wrote:
>
> Note: if the gate conditions do not improve, we may consider letting
> things merge past the deadline, but presumably that would only be for items
> that already have two cores that are +2.
>
>  dan
>
>  On Tue, Feb 19, 2013 at 3:13 PM, Dan Wendlandt <d...@nicira.com> wrote:
>
>> Hi team,
>>
>>  First couple important things from today's team meeting, particularly
>> related to gating issues.
>>
>>  - The gate is WAY behind and taking forever.  A rash of pypi issues
>> earlier this morning didn't help.  PLEASE REFRAIN FROM SUBMITTING
>> NON-BLOCKING BUGS TODAY OR TOMORROW.  Basically, if its not actively
>> preventing you from making progress on G-3, please hold off.   If its truly
>> important to have it fixed before G-3 milestone, go ahead an merge.
>>
>>  - Due to the gate being behind, ttx is moving the deadline for
>> requiring a Feature Freeze Exception by one day.  I don't see a need to
>> change any deadlines for Quantum though, so we're still operating in the
>> mode that THINGS NEED TO BE MERGED BY TONIGHT TO GET INTO QUANTUM G-3.
>>
>>  Finally, there are a lot of bugs targeted for G-3, most of which we
>> need to bump out.  There are three possibilities:
>> - keep targeted for for G-3.  Only for "critical" bugs that will impact
>> someone's ability to test the G-3 milestone.
>> - move to G-rc1.  For any bug that just needs to be fixed before we
>> release grizzly.
>> - move to H-1.  For any bug that isn't important enough or is too
>> large/risky to be included in grizzly.
>>
>>  I'll be updating bugs today at ttx's request.  sub-team leads, please
>> use the bug urls for your sub-project to make sure no bugs have been
>> misclassified.
>>
>>  Thanks,
>>
>>  Dan
>>
>>
>>
>>
>>  --
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Dan Wendlandt
>> Nicira, Inc: www.nicira.com
>> twitter: danwendlandt
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>
>
>
>
>  --
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Dan Wendlandt
> Nicira, Inc: www.nicira.com
> twitter: danwendlandt
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
>
>
> --
> Mailing list: https://launchpad.net/~quantum-core
> Post to     : quantum-core@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~quantum-core
> More help   : https://help.launchpad.net/ListHelp
>
>


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Dan Wendlandt
Nicira, Inc: www.nicira.com
twitter: danwendlandt
~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- 
Mailing list: https://launchpad.net/~quantum-core
Post to     : quantum-core@lists.launchpad.net
Unsubscribe : https://launchpad.net/~quantum-core
More help   : https://help.launchpad.net/ListHelp

Reply via email to