Move trackers from SourceForge to Trac

[Frederico Caldeira Knabben]

The new dev site is finally ready and now we have a big and important task to be done. All trackers must be moved from SourceForge to the new system.

The following trackers must be moved:

• ​Bugs
• ​Feature Requests
• ​Patches

Other trackers will be handled in a second moment.

For now, the above trackers will be disabled to public view. Only SF project members will have access to it.

Breaking the Task

For those interested on working in this task, just follow these advices so we can organize it better:

• Open the tracker list, filter it for Status=Open and sort it by ID (Ascending);
• Annotate the range of Request IDs you would like to work in;
• Add a comment to this ticket like: "I'm working on bugs from XXX to YYY".

Of course, check first if no one is already working inside your range.

General Guidelines

1. Open the report at SF. It is not required, but if possible, check that it is still valid, closing it if it's not (ignoring the next steps).

2. Create a new ticket at Trac in another window, with the appropriate Type.

2. Copy and paste the summary. Correct any typo or make it clearer, if needed.

3. Copy and paste the report body. If possible, make it more readable (line breaks and code blocks, for example).

4. At the end of the new ticket body, add the following:

----
Moved from SF:[[BR]]
http://sourceforge.net/tracker/index.php?....

The link should point to the relative report page at SF

5. If possible, set the "Component" and "Version" fields. Avoid using "Priority" and "Milestone".

6. Add "SF" to "Keywords".

7. Save the new ticket.

8. Download any attachment from the SF report and add it to the new ticket. In the Attachment Info, add the text:

{Attachment Description at SF, if any} Moved from SF. Original author: {SF user name for the attachment}

9. Copy and paste every comment from the SF report, in a chronological order (older first). Ignore duplicates, vandalism and anything that adds no value to the ticket (like "Me too!"). After the original commend, add:

----
Moved from SF. Original poster: {SF user name or Anonymous}

10. Reporter field (set to anonymous, if anonymous) and CC all comment posters (if not anonymous) using their SF user name, concatenated with @users.sourceforge.net. E.g.: fredck@….

11. Set the Status of the original SF report to "Closed". At the same time, add a comment to that report in the following format:

This report has been moved to our new development site at:
http://dev.fckeditor.net/ticket/{ticket_ID}

Duplicates

Whenever possible, avoid moving duplicates, but don't ignore them. Instead follow these steps:

1. Add a comment to the Trac ticket in this format:

The following SF report has been market as duplicate of this:
http://sourceforge.net/tracker/index.php?....

2. If any useful comment (even the report body) or attachment is available, add it to the ticket as defined at points 9 and 10 in the above General Guidelines. In addition, add the SF report URL to the comment.

3. Close the SF report as defined in the above point 11, using a comment in the following format instead:

This report has been marked as a duplicate of:
http://dev.fckeditor.net/ticket/{ticket_ID}

If the "Resolution" field is available at SF, set it to "Duplicate".

Patches

A patch is nothing else than a fix for a bug or an implementation of a new feature. So, we should just transform the patch to either a Bug or a New Feature ticket.

[Frederico Caldeira Knabben]

Ok... some people were confused because the SF trackers have been closed. I've so make then visible to the public, with a message indicating users to visit our new dev site.