On Feb 7, 2012, at 1:13 PM, Marlon Pierce wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I'd like to suggest Airavata make more use of Jira's "epic" and > "story" tags to capture higher level goals and requirements. + 1
I think we are starting to see this need now as tracking tasks doing releases is starting to get cumbersome. > The Apache Rave incubator has been doing this for the last year: see > http://incubator.apache.org/rave/issue-management.html. I don't see > the need for Airavata to be as strict as Rave on Jira report > structure, but I do think it would be a good way to codify some of our > higher level goals since the mailing list is too free form. > > One downside is that epics and stories are difficult to close. I > think Alek raised this issue early on. Rave guidelines nicely distinguish between each of these categories. May be we should follow a guideline that Epic/Stories should not be too open ended but should be confined to one release cycle. That way, we do not get too many high level Epics, rather broken down well scoped items in JIRA. Suresh > Marlon > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.17 (Darwin) > Comment: GPGTools - http://gpgtools.org > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iQEcBAEBAgAGBQJPMWnaAAoJEEfVXEODPFIDYyEIAIasnbzh7D5fygotBwUQJsCI > sG0reSUIZp9Akj/5KiQXiM0R9IHOiiJOCFVmcreXcWVG98Wq+AJuKmRPgCmYA6gd > qkxoUCqznXwkFc3b3xWUuAHzmAQYFJV2/X/MuY9uQ8SZD2ZBCgn5Iyay7BUBjWkN > 8LBHzz+pq3poROhHAHROzPj/uOIuT1+PHkhMDZk0E7/EG0pgO4Pk/Mt7+J1eoskz > CRpN7lo2dWKnMunToajV755uNzWmpadLazdAuBVZHsWgPyeR5SyWoIgCMbVoNBDG > knsgTYwnqE5X09Ae/Zy1Ouhd2S/I4eKAsP1KOH1piWic4fCMxaivRX3loZX4kMY= > =JJx+ > -----END PGP SIGNATURE-----
signature.asc
Description: Message signed with OpenPGP using GPGMail
