[Portfolio] [WG: I18N & L10N] SAK-19184: priority change from blocker to critical

[DAVID ROLDAN MARTINEZ]

Hi,

I agree because of the time constraints but I would like to remark that this tools doesn't work from an i18n point of view and this means that the issue should be set to blocker...but for next release. ;-)

David
________________________________________
De: i18n-bounces at collab.sakaiproject.org [i18n-bounces at collab.sakaiproject.org] En nombre de Anthony Whyte [arwhyte at umich.edu]
Enviado el: lunes, 10 de enero de 2011 16:13
Para: i18n at collab.sakaiproject.org
CC: osp; Alan Berg; Theriault Seth
Asunto: [WG: I18N & L10N] SAK-19184: priority change from blocker to    critical

Last Thursday during the RM call during a review of 2.8-related blocker/critical tickets I recommended that the i18n OSP SAK-19184 ticket be downgraded from a blocker in order to remove it from the list of tickets that potentially block a 2.8.0 release.

https://jira.sakaiproject.org/browse/SAK-19184

My "triage" rationale:

1) the ticket describes a pre-existing condition that is not at the same time a regression  (a key consideration in my view)
2) work on the ticket appears to have stalled around mid-November 2010
3) It is now nearly mid-January and the 2.8.0 release is scheduled for 1 March 2010.
4) I suspect there is little chance that the issue can be resolved, tested and verified between tomorrow (when I cut the next QA tag) and the follow-on QA tag that will be made available two weeks from now.   Delaying resolution any further will jeopardize the current 2.8.0 release timeline.

I recommend that work on this ticket be targeted for 2.8.1 or later.

Cheers,

Anthony