Open Stack

This sounds good, I was hoping it'd be acceptable to use etherpad. I 
filed a blueprint [1] but I'm anticipating using the etherpad much more 
regularly to track which files are being worked or completed.

[1] https://blueprints.launchpad.net/heat/+spec/mox-to-mock-conversion
[2] https://etherpad.openstack.org/p/heat-mox-to-mock

Thanks for the guidance :)

On 10/09/2015 12:42 PM, Steven Hardy wrote:
> On Fri, Oct 09, 2015 at 09:06:57AM -0400, Jay Dobies wrote:
>> I forget where we left things at the last meeting with regard to whether or
>> not there should be a blueprint on this. I was going to work on some during
>> some downtime but I wanted to make sure I wasn't overlapping with what
>> others may be converting (it's more time consuming than I anticipated).
>>
>> Any thoughts on how to track it?
>
> I'd probably suggest raising either a bug or a blueprint (not spec), then
> link from that to an etherpad where you can track all the tests requiring
> rework, and who's working on them.
>
> "it's more time consuming than I anticipated" is pretty much my default
> response for anything to do with heat unit tests btw, good luck! :)
>
> Steve
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>