#29: Coordinate Features that aren't filed ----------------------+------------------------------------------ Reporter: mattdm | Owner: Type: task | Status: new Priority: blocker | Milestone: Fedora 21 (Feature Deadline) Component: Planning | Keywords: meeting ----------------------+------------------------------------------ Here's the list:
https://fedorahosted.org/cloud/query?summary=%5EFile&status=accepted&...
These tickets are for making sure we get the changes filed. Actual tracking of the progress will be using the main feature process (no intention of adding duplication!), although we can of course also file new tickets here for tracking individual bits of work.
Why are bugtracker emails being sent to the list at all?
Robert Collins rbtcollins@hp.com Distinguished Technologist HP Converged Cloud
________________________________________ From: cloud-bounces@lists.fedoraproject.org [cloud-bounces@lists.fedoraproject.org] on behalf of cloud [nobody@fedoraproject.org] Sent: Wednesday, 2 April 2014 03:27 Subject: [cloud] #29: Coordinate Features that aren't filed
#29: Coordinate Features that aren't filed ----------------------+------------------------------------------ Reporter: mattdm | Owner: Type: task | Status: new Priority: blocker | Milestone: Fedora 21 (Feature Deadline) Component: Planning | Keywords: meeting ----------------------+------------------------------------------ Here's the list:
https://fedorahosted.org/cloud/query?summary=%5EFile&status=accepted&...
These tickets are for making sure we get the changes filed. Actual tracking of the progress will be using the main feature process (no intention of adding duplication!), although we can of course also file new tickets here for tracking individual bits of work.
-- Ticket URL: https://fedorahosted.org/cloud/ticket/29 cloud https://fedorahosted.org/cloud Fedora Cloud Working Group Ticketing System _______________________________________________ cloud mailing list cloud@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
On Tue, Apr 01, 2014 at 09:51:05PM +0000, Collins, Robert (Converged Cloud) wrote:
Why are bugtracker emails being sent to the list at all?
To be a bit pedantic, they are not actually bug tracker emails, because we're tracking work effort, not bugs. The ticket system is for organizing what we as a SIG are working on, or need to work on, or think we want to work on (and for the Cloud WG as a subset of the SIG).
The messages don't *have* to go to the list and we can certainly turn that off if it seems to be doing more harm than good, but I didn't want the tracker to turn into yet another place to look that we all forget about. I don't think there is really going to be a an overwhelming amount of ticket traffic, although there will be a mini-avalanche as we get the (not working at all) wiki todo list converted.
If you have any suggestions for doing this better, I'm all ears!
If you want to filter them out, there is an 'X-Trac-Ticket-ID:' header, by the way.
#29: Coordinate Features that aren't filed ----------------------+------------------------------------------- Reporter: mattdm | Owner: Type: task | Status: new Priority: blocker | Milestone: Fedora 21 (Feature Deadline) Component: Planning | Resolution: Keywords: meeting | ----------------------+------------------------------------------- Description changed by mattdm:
Old description:
Here's the list:
https://fedorahosted.org/cloud/query?summary=%5EFile&status=accepted&...
These tickets are for making sure we get the changes filed. Actual tracking of the progress will be using the main feature process (no intention of adding duplication!), although we can of course also file new tickets here for tracking individual bits of work.
New description:
Here's the list:
https://fedorahosted.org/cloud/query?status=accepted&status=assigned&...
These tickets are for making sure we get the changes filed. Actual tracking of the progress will be using the main feature process (no intention of adding duplication!), although we can of course also file new tickets here for tracking individual bits of work.
--
#29: Coordinate Features that aren't filed ----------------------+------------------------------------------- Reporter: mattdm | Owner: Type: task | Status: closed Priority: blocker | Milestone: Fedora 21 (Feature Deadline) Component: Planning | Resolution: fixed Keywords: meeting | ----------------------+------------------------------------------- Changes (by red):
* status: new => closed * resolution: => fixed
Comment:
Since the list is now empty and the deadline has passed, I think this is all done...