Further steps of Trac migration

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Further steps of Trac migration

Paul Sokolovsky

Per previous RFC, I'm proceeding with bugtracking migration to Trac:

1. Trac's tracker configured for usage, first bug posted.
2. SF.net native bug tracker was augmented with visible notices that
Trac should be used, but tracker renamed to "Bugs (depracated, use
3. Unused Support Request tracker was disabled.
4. All tickets from Feature Requests and Patches are being move are
Bugs, corresponding trackers to be disabled afterwards.
5. Notice are to be added to each open ticket, asking submitter to
repost the ticket to Trac.
6. Depending on user response, I'll try to migrate important tickets
myself as time permits.

Best regards,
 Paul                          mailto:[hidden email]

The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
Cegcc-devel mailing list
[hidden email]