David Mudrak
added a comment - 16/Dec/10 4:07 AM Assigning back to myself. Sorry but this issue was created per my request in the forum and I am in contact with the reporter. I do not understand why it was re-assigned from me...

It was reassigned from you because the issue was selected during our first spring meeting. Some STABLE backlog issues with high priority were reassigned to moodle.com and in the Spring pool. Then everybody from the Spring team pick some moodle.com issues from the Spring pool, fix it, pick another one, fix it ... till the end of the spring. Obviously it's our first spring ever so Agile processes will improve with the time

I'll let people know about that during our daily spring meeting. Thanks.

Jérôme Mouneyrac
added a comment - 16/Dec/10 10:09 AM - edited It was reassigned from you because the issue was selected during our first spring meeting. Some STABLE backlog issues with high priority were reassigned to moodle.com and in the Spring pool. Then everybody from the Spring team pick some moodle.com issues from the Spring pool, fix it, pick another one, fix it ... till the end of the spring. Obviously it's our first spring ever so Agile processes will improve with the time
I'll let people know about that during our daily spring meeting. Thanks.

A quick note, once is it in PULL request, the spring issue should be marked as Done (== IN PULL REQUEST). If the pull request is rejected, the issue must be reopened. It's temporary till we have some better greenhopper columns

Jérôme Mouneyrac
added a comment - 16/Dec/10 11:22 AM A quick note, once is it in PULL request, the spring issue should be marked as Done (== IN PULL REQUEST). If the pull request is rejected, the issue must be reopened. It's temporary till we have some better greenhopper columns