cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: Track feature requests in bugzilla? (was Re: DO NOT REPLY [Bug 10203] - Docs referenced by XSLT's document() are not included in cache validity)
Date Thu, 09 Oct 2003 10:13:08 GMT
Bertrand Delacretaz wrote:
>
> Le Jeudi, 9 oct 2003, à 11:42 Europe/Zurich, Bruno Dumon a écrit :
> > ...I agree it's a feature request and added it to the wiki page.
> > However,
> > can't we use bugzilla also to track (serious) feature requests? There
> > are a couple of other "enhancement" requests in there, should we also
> > close them and add them to the wiki page?
>
> We created
> http://wiki.cocoondev.org/Wiki.jsp?page=CocoonFeatureRequests Monday in
> the frenzy of the Hackathon, but IMHO (and in retrospect) having them
> in Bugzilla makes more sense.
>
> The Wiki page can then explain how we handle them and include a
> bugzilla link to the list of currently open feature requests.
>
> We have to be clear on how we separate them from bugs though, I think
> feature requests should all have priority=Enhancment, is that ok? And
> what about [PATCH]es?
>
I thought about this topic/problem as well. My first idea was to say a
feature requests is not entered into bugzilla but on the wiki page.
This would free us from many open bugzilla entries.
And we also create a process in the following way:
- the wiki feature request page is scanned from time to time (the mails
  help there)
- A new entry is evaluated (perhaps the feature doesn't make sense or
 is a bug or is a really cool thing etc.) and if accepted added
  to our planning document.
So the planning document in our docs contains the approved list of feature
requests.
I'm planning to "reactivate" our planning documentation in the docs section
so that it show more information anyway.

I'm not sure if this is a good procedure or not. What do you think?

Carsten


Mime
View raw message