Is my project a Classic or a Beta project?

Not sure whether you have a Classic or Beta project? The best way to tell is to look at the navigation bar.

A classic project will start with Summary, Files, Support and Develop, and (if you're logged in as a Project Admin) will end with Project Admin like so:

A Beta project has a customizable navigation bar, so it may not appear in the same order, however, the Admin tool will always show for project administrators. A project created with the default toolset looks like this:

What are the differences?

• The SourceForge 2.0 Beta system is running the Allura platform, and it has an updated feature set compared to the classic system.

• The permissions system for beta projects is much more flexible.

• The forums and ticketing systems have been completely rewritten. The new tools are much more flexible than the forums and Tracker from classic projects.

• There are new tools included in the platform, such as the wiki and blog tools. The Beta also supports subprojects.

• Development for the Beta system is ongoing, whereas development on the classic system has stopped. While the Beta will continue to improve, the classic system will continue to grow more and more out of date.

• And perhaps the biggest difference between the classic and beta systems: allura itself is Open Source! You can check out the code here, and you can even contribute code to help make the system better!

Unless you have a specific reason to use the classic system, we suggest you try the Beta.

What's the same?

The following features are the same whether you use a classic or Beta project:

• File Release System
• Project web
• Hosted Apps
• Mailing Lists

Why would I want to use a classic project?

While in many regards, the Beta system is a considerable update, with greater flexibility and functionality, there are a few reasons why you might still want to consider using a classic project:

• The classic system supports CVS, SVN, Git, Mercurial and Bazaar, whereas the Beta system only supports SVN, Git and Mercurial.

• Classic projects allow direct access to the repositories using the shell service. If you need to access your repository via the shell, you should use a classic project.

• We do not currently have an interface for accepting donations in Beta projects. You may still accept donations for your project, we just don't have a built-in interface for that yet. The classic system only has an interface for PayPal, so if you want to accept donations using any other method, there is no difference between classic and beta projects.

• The Help Wanted system is not available for Beta projects yet. With that said, as the Help Wanted system for classic projects is fairly outdated; we are planning a re-write of that tool for the allura platform so once that is complete it should be much improved over the current Help Wanted system.

I want to switch to the other platform, can I?

Beta -> Classic:

It is not possible to migrate a Beta project to a Classic project. If you'd like to switch to the classic system, we'll need to remove your project so you can re-register it as a classic project.

This will remove all data for the project, so make sure you back everything up so that you can set your project back up again. If you'd like to do that, please log a support ticket requesting the project removal.

Classic -> Beta:

We have a migration script that the team is working on, however it is not complete. Most items can be migrated, but not everything. If you are interested in migration, see Project Admin -> Settings, then on the right Opt-in Migration for a current list of what items are, and are not, supported via the migration.