the holy grail will be meshing with a revision control system so that releasing of functionalities can be done without having to directly interact with revision X and revision Y...but I guess we can't solve all of the issues all at once, have to save something for later
jesse On 1/3/06, Jason van Zyl <[EMAIL PROTECTED]> wrote: > > Jesse McConnell wrote: > >> with that short list we: > >> > >> - pick the issue at hand > >> - burst of discussion on the list > >> - secretary captures the salient points > >> - offers up the document for review > >> - go back to discussion/capture/review until complete > >> - a final document then accompanies the resolution and the issue is > closed > > > > > > > > looks good to me, I like it...can even setup a custom workflow in jira > so > > that issues that are marked 'open for discusion' are the ones that spam > > weekly reminders to the email list > > Cool, I've never done a custom workflow in JIRA so I wouldn't mind some > help with that. > > I think what we're going to end up here is a good model for any project > and if we can hook in the tools to help automate much of the tedious > work it will rock. I just don't want to get to tied into JIRA. I really > want that issue management API! :-) > > > > jesse > > > > -- > > jesse mcconnell > > jesseDOTmcconnellATgmailDOTcom > > > > > -- > jvz. > > Jason van Zyl > jason at maven.org > http://maven.apache.org > > We know what we are, but know not what we may be. > > -- Shakespeare > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- jesse mcconnell jesseDOTmcconnellATgmailDOTcom
