We should be clear that just because Jira has that helpful 'Roadmap' panel, doesn't mean it's our official roadmap. It really isn't, though that is how Jira would like us to do things. I can't speak for everyone, but Jira, to me, is just a tool, it's not the boss of me.
B. On 9 February 2011 12:30, Jan Lehnardt <[email protected]> wrote: > > On 9 Feb 2011, at 09:26, Benoit Chesneau wrote: > >> On Tue, Feb 8, 2011 at 10:02 PM, Noah Slater <[email protected]> wrote: >>> >>> On 8 Feb 2011, at 20:53, Benoit Chesneau wrote: >>> >>>> What is it supposed to mean ? A roadmap is a "a detailed plan to guide >>>> progress toward a goal " . Why couldn't we define goals ? >>> >>> I think Jan's point is that we use the JIRA roadmap as an advisory only, >>> and never state that we are committing to it. That means that if I create a >>> ticket for CouchDB to be able to read and send email, it doesn't hold-up >>> the project. >>> >>> "Every program attempts to expand until it can read mail. Those programs >>> which cannot so expand are replaced by ones which can." >>> >>> — Jamie Zawinski >>> >> >> hum, ok yes a ticket is only a ticket. Although I was under the >> impression that we can give some priority to the tickets or close them >> if they doesn't enter in project goals. > > All I'm saying is that just creating a ticket and assigning it a version > number won't make us commit to delivering that. > > Of course we should organise all tickets into versions and come up with > a sensible batch of stuff to work towards for every release. > > Cheers > Jan > -- > > > >
