0962 is up next

One question comes to mind about bug tracking : shouldn’t FlySpray be purged of everything 0.9.7 since we moved to a new infrastructure ? Second question, does 0.9.6.x bug tracking still remains @FlySpray or will it too be switch over to JIRA ?

In JIRA 5 bugs (6 bugs #MODX87 bug is relating to the installer and a correction has been proposed) are still unresolved.
But could we deduce that all the previous bugs in FlySpray have been corrected ? If yes, sorry for this pointless alarm.

And now how could we organize to deliver this new release ? I am ready to contribute.

Migrating from Flyspray to JIRA is a manual process. Bugs have not been all that well-tracked either, honestly. I’d love to close as many out as possible in Flyspray and migrating the ones that make sense to JIRA.

I’ve got a log of issues in my "096" bookmarks folder I’d like to see resolved as well ... for any marked complete/requires testing I think a test of the SVN dump would suffice and we could just close them out completely.

I am available to help with 0962, feel free to assign me any tasks. I will take a look at the open issues and see if anything is within my understanding.

If you need someone to do something like transfering bugs from FlySpray to JIRA, I’ll list what’s to be done and see if that’s really such a big task... or maybe you can at least close FlySpray to new tickets ?

I’ve got a log of issues in my "096" bookmarks folder I’d like to see resolved as well ... for any marked complete/requires testing I think a test of the SVN dump would suffice and we could just close them out completely.

So, as David, could I suggest
1/ to close Flyspray to new tickets (May be already done)
2/ analyse the existing Flyspray tickets :

Implemented (3) - test that the SVN includes the correction and if ok close them definitively

Waiting on user (2) - ?? May ask to the sender some precisions otherwise change the status to unconfirmed

Require testing (10) - redo the test and the change the status to complete

Researching (3), - Investigate to solve the bug

Assigned (3) - ?? May be ask to the person in charge of the correction what i the current status of the correction. 2 bugs are assigned to Bravado and 1 to Pixelchutes.

Unconfirmed (3) - redo the test and decide of a new status

As soon as all the Flyspray tickets are "completed" or "unconfirmed", close all the tickets

3/ decide which jira tickets should be corrected for the 0.9.6.2

4/ As soon all the tickets are solved, package the last release and publish it.

If you agree with this logical task list, a larger communication to all "testing & qa" + "coding" contributors could accelerate the process of the 0.9.6.2 delivery.
Do you agree with this proposal ?

That sounds great to me. The default status of bugs is unconfirmed and we don’t have to fix everything for 0962 ... there’s always 0963.