[openstack-dev] [qa] Should Assignee, Milestone really be in the qa-spec?

Frittoli, Andrea (HP Cloud) frittoli at hp.com
Wed Jun 11 19:42:33 UTC 2014

+1, I would remove them as well, assignee and milestone probably do not need
to go through review, it something we can agree upon at QA meetings.


-----Original Message-----Cl at ud3D3bu$$y
From: David Kranz [mailto:dkranz at redhat.com] 
Sent: 11 June 2014 20:18
To: OpenStack Development Mailing List
Subject: [openstack-dev] [qa] Should Assignee, Milestone really be in the

While reviewing some specs I noticed that I had put myself down for more
Juno-2 work than is likely to be completed. I suspect this will happen
routinely with many folks. Also, assignees may change. This information is
not really part of the spec at all. Since we are still using blueprints to
actually track progress, I think it would be better to use the corresponding
fields in blueprints to make sure these values reflect reality on an ongoing


OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6199 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140611/5346d551/attachment.bin>

More information about the OpenStack-dev mailing list