reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mariia Mykhailova <mamyk...@microsoft.com>
Subject RE: JIRA descriptions
Date Thu, 21 Apr 2016 17:37:45 GMT
+1 
Especially when discussions happen on PR, since Github comments can be harder to read than
JIRA ones (JIRA doesn't collapse them)

-Mariia

-----Original Message-----
From: Julia Wang (QIUHE) [mailto:Qiuhe.Wang@microsoft.com] 
Sent: Thursday, April 21, 2016 10:36 AM
To: dev@reef.apache.org
Subject: RE: JIRA descriptions

+1

It does change when we move along. So should go back to update it to reflect what we are doing.


-----Original Message-----
From: Markus Weimer [mailto:markus@weimo.de] 
Sent: Thursday, April 21, 2016 10:34 AM
To: dev@reef.apache.org
Subject: JIRA descriptions

Hi,

we seem to have lots of design discussions over on GitHub these days. 
Typically, those lead to changes that are not reflected in the initial JIRA description. Similarly,
the JIRA description gets outdated quickly when we discuss on JIRA itself.

This makes it hard to browse the JIRA for an issue, as one has to parse the JIRA comments
and more often than not the GitHub discussion of the related pull requests to understand the
final design.

Hence, I wonder: Should we make an effort to update the JIRA description with the design as
it evolves? That way, it will reflect the final design when we merge the code. This might
not be realistic for "small" 
changes, but for the "big" ones which have sub-items, it should be doable.

What do you think?

Markus
Mime
View raw message