[ckan-dev] Github Issues

Wed Jan 9 12:52:29 UTC 2013

Any chance we can have the default github issues tags (bug, enhancement,
duplicate, invalid, question, wontfix) back? These seem useful to me,
maybe it's just that I like tagging things, but making an issue and
leaving it completely untagged/unsorted seems like it's just going to
get lost:

bug/enhancement -- useful for e.g. seeing what important bugs still need
to be fixed for a release, making a list of "known issues" for a CKAN
release, seeing what feature requests there are to consider for next
release

question -- useful to separate support requests from bug reports and
feature requests, in case people start using github to ask support
questions

duplicate, invalid, wontfix -- useful to use just before you close an
issue so people can see why it was closed, perhaps enter a comment
saying why as well, seems equivalent to on trac where you could set the
status to one of fixed, wontfix, duplicate, etc.

On Tue, Dec 18, 2012 at 04:41:13PM +0000, David Raznick wrote:
> Hello All
> 
> I have turned github issues on for CKAN.  Good news is that all pull
> requests are already there and makes them easy to see which ones are
> assigned to you.
> 
> I have only added 4 labels. Priorty based ones and a CKAN 2.0 is for stuff
> that *must* get fixed for the release.
> 
> We will not yet move over any tickets from trac and we hope to keep the
> issue list clean and try and avoid anything that we do not intend to work
> on over the next couple of months (maximum).  All future and nice to have
> ideas should be discussed somewhere else in order to avoid clutter and they
> should be purged regularly.
> 
> A good reference to understand how it works seems to be this blog article.
> 
> https://github.com/blog/831-issues-2-0-the-next-generation
> 
> It tells you how to make your commit messages to come up/close an issue.
> 
> Please feedback any further tips that are useful.
> 
> Thanks
> 
> David

> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev