Project

Profile

Help

Task #91

Updated by bmbouter over 5 years ago

This should leverage the cloning code written in #90 and needs to be done after #90 is completed. This task is to coordinate and move the remaining non-closed bugs from Bugzilla to Redmine.

h3. The moving aspects

Follow the same process as in #90 except move bugs from this search [0] instead. Also, mark them as 'Issues' in Redmine since they are defects. Similar to #90, do not copy over 'blocks' field, that will be handled by a later Task #92. Update the Bugzilla state similarly as recommended in #90.

As a reminder: %{color:red}Determine if the issue is private in Bugzilla. If it is private in Bugzilla then the bug created in Redmine needs to also be private.%

Similar to #90, the code should be kept playpen so that it is available to others. No API keys or passwords should be stored in this code.

h3. The community aspects

There are several aspects to cut over the community besides moving bugs.

1. Pick a 'cutover' time.

2. Let the community know. mhrivnak and bmbouter thought 48 hours is enough notice to give the community. E-mail the Pulp mailing list indicating that the issue tracker is moving and what its new location is. Also indicating the new Redmine install is going to be used for stories, tasks, sprint planning, etc. would be good too. Publishing a blog post may also make sense. Have others review the notes before they are sent to get the messaging clear.

3. Work with the Front Line Support team Bugzilla maintainers (bugzilla-requests@redhat.com) to disable plan a coordinated switch of the 'Open for new bugs' checkbox. This will prevent new bugs from Pulp Bugzilla page into read-only mode if they are able to do that. Once the cutover occurs we can't have old issues being filed against the Pulp component. The Front Line Support team is available 24x5 so coordinating a time should be do-able. The product name we want to adjust is named 'Pulp'. component in bugzilla.

4. Push a docs fix onto the existing supported release streams updating our docs on how/where we file bugs AND stories. This should likely be pushed near the time of the cutover. It will be tricky to update these docs without merging forward the '2.X-release' branches into each other. We should avoid merging forward '2.X-release' branches.

5. Notify the community once the cutover is complete.

[0]: http://tinyurl.com/p2duznn

Back