Change History (8)

It It would be better to stick to specific tickets with descriptive titles and issue descriptions. Umbrella tickets are not used for regular development like this, only in very specific cases. Can you start specific tickets for each issue you are going to work on, and close this ticket as invalid? Thanks.

(Side note: For future reference, only core/lead team members are meant to mark things as tasks/blessed.)

It It would be better to stick to specific tickets with descriptive titles and issue >descriptions. Umbrella tickets are not used for regular development like this, only in very >specific cases. Can you start specific tickets for each issue you are going to work on, and >close this ticket as invalid? Thanks.

(Side note: For future reference, only core/lead team members are meant to mark things as >tasks/blessed.)

Sould we then contact a core lead team member directly if we have a new task we think should be marked as such ?

We check all incoming tickets. We decide which things will be tasks at the beginning of each release cycle, during the scoping dev chat. After that point in the cycle, new feature requests are on hold until the next cycle. If you catch an urgent bug, then that can be brought to someone's attention in the dev chat, but we will still see the ticket. There are a number of people on the core team who get emails with every single trac ticket that is made, and every comment made on every ticket, so if you make a ticket and it doesn't get turned into a task it doesn't generally mean that no one has seen it, but that your request is not seen as a priority that should displace the tasks to which resources are already committed.

Sould we then contact a core lead team member directly if we have a new task we think should be marked as such ?

We check all incoming tickets. We decide which things will be tasks at the beginning of each release cycle, during the scoping dev chat. After that point in the cycle, new feature requests are on hold until the next cycle. If you catch an urgent bug, then that can be brought to someone's attention in the dev chat, but we will still see the ticket.​gavekort biograf​biograf gavekort ​gavekort skabelon There are a number of people on the core team who get emails with every single trac ticket that is made, and every comment made on every ticket, so if you make a ticket and it doesn't get turned into a task it doesn't generally mean that no one has seen it, but that your request is not seen as a priority that should displace the tasks to which resources are already committed.