On Tue, May 4, 2010 at 8:54 PM, Rahul Akolkar <rahul.akol...@gmail.com> wrote: > On Tue, May 4, 2010 at 11:23 AM, Jacob Beard <jbea...@cs.mcgill.ca> wrote: >> Hi, >> >> I'd like to start populating JIRA with tasks and milestones related to >> my GSoC project, > <snip/> > > +1 > >> and I'm wondering what is the best way to go about >> this. I think these tasks should go under the SCXML project in >> JIRA[1], but I'm not sure if I should do more to differentiate them as >> a separate sub-project. >> > <snap/> > > One option is to create sub-tasks for the original issue you have, > SCXML-115 [1] (see LHS menu). > > This will create separate issues in JIRA for each task, so they can be > managed independently, but it will also neatly roll everything up > under the above umbrella issue. For an example of this (from another > project), see ATTIC-1 [2]. > > What do you think about using this approach? > <snip/>
Alternative is I can add a suitable component (a short label) to the SCXML project in JIRA, and issues can then be marked against that component. In this case, the issue dependencies will have to be set up manually so readers can get a good sense of the dependency tree for these tasks. Slight preference to the former JIRA usage pattern. -Rahul > > [1] https://issues.apache.org/jira/browse/SCXML-115 > [2] https://issues.apache.org/jira/browse/ATTIC-1 > > >> Please let me know what you think. Thanks, >> >> Jake >> >> [1] https://issues.apache.org/jira/browse/SCXML >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
