announcements

Download

announcements@common-lisp.net

April 2015

1 participants
1 discussions

Migration of common-lisp.net CVS repositories -- GitLab push e-mail configuration
by Erik Huelsmann 11 Apr '15

11 Apr '15

Hi, This mail serves to announce two common-lisp.net related news items: 1. CVS repository migration 2. GitLab push e-mail configuration FAQ added == CVS repository migration == As previously discussed on clo-devel(a)common-lisp.net, common-lisp.net is dropping support for CVS [1]. To that extent, projects which have CVS repositories will receive an e-mail over the coming weeks offering the choice to migrate to Subversion or Git. Mails and migrations will be sent out in batches, so members may not receive messages for all projects at once. The default migration is to Git+GitLab [2]. Projects can request migration to Subversion+Trac when Git isn't acceptable. If projects want to file a request to migrate to Subversion in advance of their migration notice, please file a ticket at https://trac.common-lisp.net/clo/newticket After migration, the CVS repository will no longer be accessible. After all CVS repositories have been migrated, the following services will be scrapped: * Anonymous CVS checkout * ViewVC webbrowsing (for Subversion already available through Trac) [1] https://mailman.common-lisp.net/pipermail/clo-devel/2015-February/000934.ht… [2] https://gitlab.common-lisp.net/ == GitLab push e-mail configuration == Some projects had push e-mail configured in conjunction with their <project>-cvs(a)common-lisp.net mailing list. Due to the migration to GitLab, this functionality stopped working. Today, we've published a FAQ item detailing how to configure GitLab and Mailman to get the same result. See https://common-lisp.net/faq/emailonpush/ how to get this configuration for your project. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.

1 0