#3838 File F-14 rel-eng ISO tickets early

Created 6 years ago by jlaska
Modified 23 days ago

Greetings, during the [https://fedoraproject.org/wiki/Fedora_13_QA_Retrospective#Release_Engineering Fedora 13 QA retrospective], it was identified that the tickets used to track QA ISO drops were tremendously useful, but often not created ahead of time. This ticket is intended to trac any changes or recommendations to improve the situation. I'm not sure if you'd like to create all F-14 rel-eng tickets ahead of time, or establish some other process.

The hope is that we could collaborate on these tasks ahead of time and avoid filing tickets that would only be CLOSED DUPLICATE.

I was slightly late filing the Alpha tickets. As soon as Alpha is released I plan on filing the beta tickets, and so on. I don't necessarily want to pre-file them too far in advance, it clutters the screen somewhat, also it looks bad from a ticket response time (should we ever get the metrics plugin working)

Probably the best thing to do is have a schedule item that is "file tickets for X" where X is each of Alpha/Beta/Final milestones. The deadline for getting those filed should be a few weeks before the first item would be due.

Thoughts?

I was slightly late filing the Alpha tickets. As soon as Alpha is released I plan on filing the beta tickets, and so on. I don't necessarily want to pre-file them too far in advance, it clutters the screen somewhat, also it looks bad from a ticket response time (should we ever get the metrics plugin working)

Probably the best thing to do is have a schedule item that is "file tickets for X" where X is each of Alpha/Beta/Final milestones. The deadline for getting those filed should be a few weeks before the first item would be due.

Thoughts?

I added three tasks to the schedule to see if we like it. See tasks 4, 32, and 52.
http://poelstra.fedorapeople.org/schedules/f-14/f-14-releng-tasks.html

I added three tasks to the schedule to see if we like it. See tasks 4, 32, and 52.
http://poelstra.fedorapeople.org/schedules/f-14/f-14-releng-tasks.html

Replying to [comment:1 jkeating]:

I was slightly late filing the Alpha tickets. As soon as Alpha is released I plan on filing the beta tickets, and so on. I don't necessarily want to pre-file them too far in advance, it clutters the screen somewhat, also it looks bad from a ticket response time (should we ever get the metrics plugin working)

Oh yeah, I didn't think about how that might impact ticket response times.

Probably the best thing to do is have a schedule item that is "file tickets for X" where X is each of Alpha/Beta/Final milestones. The deadline for getting those filed should be a few weeks before the first item would be due.

Thoughts?

Sounds like a plan, that should eliminate any confusion.

Replying to [comment:1 jkeating]:

I was slightly late filing the Alpha tickets. As soon as Alpha is released I plan on filing the beta tickets, and so on. I don't necessarily want to pre-file them too far in advance, it clutters the screen somewhat, also it looks bad from a ticket response time (should we ever get the metrics plugin working)

Oh yeah, I didn't think about how that might impact ticket response times.

Probably the best thing to do is have a schedule item that is "file tickets for X" where X is each of Alpha/Beta/Final milestones. The deadline for getting those filed should be a few weeks before the first item would be due.

Thoughts?

Sounds like a plan, that should eliminate any confusion.

create rel-eng tickets from .ics file (python)
create-tickets.py

create rel-eng tickets from .ics file (python)
create-tickets.py

I was curious how this would work, so I wrote a quick script to demonstrate using the python-offtrac libarary and the rel-eng schedule (.ics) to create tickets from the VTODO items in the schedule. If this is helpful, we can tweak the calendar (or use another data input) so that the VTODO's match what you want as tickets.

NOTE: this requires downloading and setting the PYTHONPATH to [http://codespeak.net/icalendar/ iCalendar].

I was curious how this would work, so I wrote a quick script to demonstrate using the python-offtrac libarary and the rel-eng schedule (.ics) to create tickets from the VTODO items in the schedule. If this is helpful, we can tweak the calendar (or use another data input) so that the VTODO's match what you want as tickets.

NOTE: this requires downloading and setting the PYTHONPATH to [http://codespeak.net/icalendar/ iCalendar].

This would be super cool! The only gotcha is that the ics file does not contain the complete schedule. And the complete schedule does not contain all the tasks in the full ticket list: https://fedoraproject.org/wiki/Release_Engineering_Release_Tickets

This would be super cool! The only gotcha is that the ics file does not contain the complete schedule. And the complete schedule does not contain all the tasks in the full ticket list: https://fedoraproject.org/wiki/Release_Engineering_Release_Tickets

Replying to [comment:5 poelstra]:

This would be super cool! The only gotcha is that the ics file does not contain the complete schedule. And the complete schedule does not contain all the tasks in the full ticket list: https://fedoraproject.org/wiki/Release_Engineering_Release_Tickets

Aha, great link! I could easily key off of that wiki page instead. Let me know if you think this would make life easier for ticket'ing.

Jesse, one thought. Is there a way to add more detail to those RATS tickets? Right now, it's hard to tell which ticket corresponds to which task on the schedule. Maybe adding the task in the Summary, or as a keyword? Dunno. For example, we have 3 RATS drops upcoming, but there is only 1 ticket listed. How would you prefer handling that?

Replying to [comment:5 poelstra]:

This would be super cool! The only gotcha is that the ics file does not contain the complete schedule. And the complete schedule does not contain all the tasks in the full ticket list: https://fedoraproject.org/wiki/Release_Engineering_Release_Tickets

Aha, great link! I could easily key off of that wiki page instead. Let me know if you think this would make life easier for ticket'ing.

Jesse, one thought. Is there a way to add more detail to those RATS tickets? Right now, it's hard to tell which ticket corresponds to which task on the schedule. Maybe adding the task in the Summary, or as a keyword? Dunno. For example, we have 3 RATS drops upcoming, but there is only 1 ticket listed. How would you prefer handling that?

Ah, clearly we should have a RATS ticket for each drop, and we should name them appropriately so that you can track them appropriately.

Ah, clearly we should have a RATS ticket for each drop, and we should name them appropriately so that you can track them appropriately.

I created two more tickets, and they are all labeled as #1, #2, and #3 respectively.

I created two more tickets, and they are all labeled as #1, #2, and #3 respectively.

I've now added three test image tickets to our Alpha ticket list. This should ensure that we get three tickets for ya'll to track for each of the drops.

I've now added three test image tickets to our Alpha ticket list. This should ensure that we get three tickets for ya'll to track for each of the drops.

Login to comment on this ticket.

cancel