SourceForge Project Migration?

Paul Julius <[email protected]> Wed, 9 Jan 2013 15:20:55 -0800
Newsgroups gmane.comp.java.cruise-control.devel
Message-ID <CA+XRcNUYc9Qsz8WVkR=YFM+D6XGkdK9=Zyp+EKU-o2mgJBFwKQ@mail.gmail.com>
Hi CruiseControl Devs,

Thoughts on this email we received from SourceForge? I know that there
has been some effort in the Github direction. Should we move off SF
altogether?

- PJ

==================================

Dear cruisecontrol project admin,

Since your project has shown some activity in the last few months, we
want to be sure that you're aware that some changes are happening at
SourceForge, and we want to be sure you're not caught by surprise.

As you may already be aware, SourceForge is upgrading to a new platform
(code-named Allura), and as a result, we'll be retiring the Classic
SourceForge platform, which your project is still using. Our goal is to
have everybody off of the old platform in the first quarter of next
year, so that we can retire that code and focus our attention on the new
platform. It would, of course, be preferable if you migrate your own
project in your own time.

You can read more about the new platform at
https://sourceforge.net/p/upgrade/ and then, when you're ready, press
the Upgrade button next to your project name.

If you have any concerns about the process, or if your project has an
unusually large number of forums, source code repositories, or trackers,
please don't hesitate to contact us to discuss your upgrade. It's
important to us that it go smoothly.

As always, thanks for being part of the SourceForge community.



Rich Bowen
SourceForge Community Manager
[email protected]

------------------------------------------------------------------------------
Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
and much more. Keep your Java skills current with LearnJavaNow -
200+ hours of step-by-step video tutorials by Java experts.
SALE $49.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122612