Openkore.com

Project Upgrade

Upgrading your project to the Allura platform gives you access to some great new features, including custom tracker fields, integrated wiki, blog and code browsing tools, threaded discussions, and more! Here are changes you can expect to see when you upgrade your project:
Will be upgraded
At this time, we are able to update the following aspects of your project:
Meta-data (name, description, trove categories, etc)
Members and permissions
Project News
Forums
Hosted Applications and Project Web
Virtual Host configuration and MySQL databases
Git, Subversion, Mercurial, Bazaar and CVS repositories
Mailing Lists
Tracker data
Project Donations*
Will not be upgraded
These items will not be moved to your upgraded project:
Project Help Wanted
SCM stats, Forum stats, Ticket stats & Traffic stats
Trac will no longer integrate with SVN
Waiting for one of these features?
The links above will take you to our engineering ticket for that feature. On the ticket, click the "+" icon to vote for it, so we know it's important to your project.
Will work exactly the same
These items will continue to function they way they currently do:
Project summary page
File releases and download stats
Project Reviews
Note that the URLs used to access your code repositories will change, and an email will be sent to all project developers with the new URLs after the upgrade is complete.
Once you click Upgrade, the upgrade will be scheduled and will begin shortly. Any changes made to your project while the upgrade is in progress may not be reflected in the upgraded project.
*If you have donations enabled, there will be a Donate link that will allow donations. However, it will be a direct link to the PayPal donation page, and individual donors will no longer be tracked or displayed.
Prior to upgrading, you can obtain a copy of your project's data as an XML file by clicking on the project name, selecting Project Admin » Features, then selecting XML Export.

isieo wrote:The people who are mainly affected are probably people who uses svn directly.

I will commence the update after 3 days of this post so that everyone will have time to switch the repo url.

kLabMouse wrote:There should be some simple way for them, to update their files without much headache.

OpenKore, it's time to upgrade your classic SourceForge project

Dear OpenKore 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.

kLabMouse wrote:You can read more about the new platform at https://sourceforge.net/p/upgrade/

the SVN url changes a bit, and the "CIA" IRC bot need some upgrades.
From the other hand, the SVN mirror needs to be upgraded too, so the package uses new URL upon "Platform Upgrade".
And the proper Anouncment placed, to warn users that Try to update their OpenKore packages using SVN tools.

EternalHarvest wrote:

kLabMouse wrote:You can read more about the new platform at https://sourceforge.net/p/upgrade/

So secret you need to log in just to read it. And even then, it's just a 403 response.

the SVN url changes a bit, and the "CIA" IRC bot need some upgrades.
From the other hand, the SVN mirror needs to be upgraded too, so the package uses new URL upon "Platform Upgrade".
And the proper Anouncment placed, to warn users that Try to update their OpenKore packages using SVN tools.

There's no justification in breaking old URLs. Sourceforge serves svn over http, won't usual redirects work in such a setup even if they want to shuffle URLs around so badly? If old URLs will stop working with so-called "upgrade", we may as well jump to another platform.

But don't mind me, whatever.

EternalHarvest wrote:We aren't really into current sourceforge platform anyway, we're using only subversion and that's all, right? Try to bug them to keep old repository URL working (and don't initiate upgrade otherwise), that's all we need.