Who would have the burden of assigning and managing epics? Thanks,
Gary. On Tue, Aug 4, 2015 at 3:08 PM, Ariel Weisberg <ariel.weisb...@datastax.com> wrote: > Hi all, > > I am playing with using an Agile board to track what goes into each > Cassandra release. What slips from release to release, as well as what is > added after the initial set of tasks for a release is started. > > You can see the SCRUM agile board I created here > < > https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=83&view=planning.nodetail&selectedIssue=CASSANDRA-9908&epics=visible > > > . > > The board has two ways to bucket issues. One is the release in which the > issue is supposed to be fixed. The other is Epics. Epics are not associated > with a release so a feature like 8099 might have an epic. Epics can be used > to bucket issues within a release or across releases. > > I would characterize Epics as being a lot like labels that integrate with > the Agile board. You can use labels with Agile boards by adding quick > filters to select on labels. > > The current set of issues types associated with the C* project in ASF JIRA > doesn't include Epic or Story. I don't use Story, but Epic would be useful > for further categorizing things. > > When I asked ASF Infra about it they said that this needs discussion and > approval by the PMC. > > Thanks, > Ariel >
