[katello-devel] Proposal: Feature Tracking and Release Planning

[Ivan Nečas]

On 11/12/2012 10:26 AM, Lukas Zapletal wrote:
> On Mon, Nov 12, 2012 at 10:21:44AM +0100, Ivan Necas wrote:
>>> -1
>>> I really like Bugzilla for its really good filtering capabilities.
>> I hate Bugzilla because it's slow as hell. But I have no issues if
>> we track the features in there. What I miss is clear connection
>> between design, code and roadmap.
>>
>> I don't like long discussions about what tool to use, because at the
>> end, it doesn't matter what we use. What matters is how we use it.
>> The first step is to admit that we have a problem:)
> Yeah, I am also for giving it a try instead long discussion - let's see
> if it helps or not. But we definitely need to improve in this. Having
> our roadmap in GH Issues won't stop users from asking on the channel.
But the difference comes, when you have a link to *up-to-date* site with 
all that info. And whatever road we choose, it will still require some 
work of ours. Choosing the right tool it will just hurt less.

I can imagine, that all our commits would have a BZ number at the 
beginning. That would require to create a BZ ticket before implementing 
anything and use the BZ as the tool for discussing features and planning 
releases for Katello. We could also make it clear in what release will 
be given bug fixed. And what release was a feature introduced in.

Keeping the number of tools low is important because every tool makes 
the process more complicated. Therefore using BZ as a tool for tracking 
features should be considered as well.

-- Ivan
>
> We should consider starting to post about features (maybe sprint tasks) on
> user/devel lists. We should put this onto our end-of-sprint task list
> (or beginning-of-sprint maybe). We already do on the devel list, maybe
> we should post also on the user list.
>
> LZ
>