Guidelines for issue trackers?
Gil Forcada Codinachs <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <CAKSaQ1_gfe4ANsN9aSoL7tECnzD_L1aFAPa2VoYsU=Mra1epoA@mail.gmail.com> |
Hi all, could the FWT in their next meeting, or whoever, make a decision on which repositories on github can enable issue trackers and which don't? I was about to report a bug on plone.app.discussion but the issue tracker is not enabled there. Should I enable it? Should I report it on Products.CMFPlone? Should I report it on Plone? IMHO all repositories should enable issue trackers but put communicate that reports are expected to land on Plone, where they will be triaged[1]. Cheers, Gil [1] yeah I know you can not automatically move them, but as you reference them from other issues I guess that's even better: the reporter doesn't have to remember the new location while developers can look at things where they belong. Does that make sense? ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ Plone-developers mailing list Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/plone-developers