That DoD looks fine to me with one small exception: I wouldn't
consider *Automate
tests (where possible)* as a requisite because then we need to define *when
is possible*. I think it is a good idea to automate as much as possible but
I just wouldn't add it to the DoD. On the other hand, I would include a
"code format meets team formatting standards".
JOSE MIGUEL GALLAS OLMEDO
ASSOCIATE QE, mobile
Red Hat
<
https://www.redhat.com/>
M: +34618488633 <
http://redhatemailsignature-marketing.itos.redhat.com/>
<
https://red.ht/sig>
On 14 December 2017 at 16:58, Luigi Zuccarelli <lzuccare(a)redhat.com> wrote:
We had our team intro (MCP Service Team 2 - we need to change this
name :)
) and the discussion of "Definition of Done"
The consensus was to get input form all teams to get some agreement and
alignment.
Any thoughts ?
Here <
https://docs.jboss.org/pages/viewpage.action?pageId=23724515> is
the link to the BF/Core team's DoD.
Luigi
--
LUIGI ZUCCARELLI
Associate MANAGER ENGINEERING , REDHAT MOBILE
Red Hat Mobile <
https://www.redhat.com/>
Communications House Ireland
Cork Road Waterford City
X91NY33
lzuccare(a)redhat.com M: +353852156995 IM: lzuccarelli
<
https://red.ht/sig>
TRIED. TESTED. TRUSTED. <
https://redhat.com/trusted>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev