+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.
andrea -----Original Message-----Cl@ud3D3bu$$y From: David Kranz [mailto:dkr...@redhat.com] Sent: 11 June 2014 20:18 To: OpenStack Development Mailing List Subject: [openstack-dev] [qa] Should Assignee, Milestone really be in the qa-spec? 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 basis. -David _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
