jsoncpp-devel Mailing List for json-cpp

FY,. Project migration completed.

Repository access is still possible through HTTPS:
https://svn.code.sf.net/p/jsoncpp/code/trunk/jsoncpp

(see code tab for all access mode of project's repository)

Baptiste.

---------- Forwarded message ----------
From: SourceForge.net <nor...@in...>
Date: 2013/4/22
Subject: SourceForge Project Upgrade - Code Repo Complete
To: no...@in...


Your code repository in upgraded project jsoncpp is now ready for use.

Old repository url: http://jsoncpp.svn.sourceforge.net/svnroot/jsoncpp

New repository checkout command: svn checkout --username=blep svn+ssh://
bl...@sv.../p/jsoncpp/code/ jsoncpp-code

You should do a checkout using the new repository location.  The old
repository is read-only now.

For more detailed instructions on migrating to your new repo, please see
https://sourceforge.net/p/forge/community-docs/Repository%20Upgrade%20FAQ/

FYI, sourceforge plan to upgrade project to their new platform.

I already tested on another projects and it seems to be harmless.

According to documentation, main will probably be that URL used to access
the subversion repository changes.

I plan to trigger the migration on 2013/04/16.

Baptiste.

---------- Forwarded message ----------
From: SourceForge.net Team <no...@so...>
Date: 2013/4/5
Subject: SourceForge project upgrades start April 22
To: bap...@gm...


Dear SourceForge project member,

As you're no doubt already aware, we're in the process of upgrading
projects to our new developer platform. The new platform is named Allura,
and is in incubation at the Apache Software Foundation
(http://incubator.apache.org/allura/).

In recent weeks, we've been upgrading projects that have been inactive for
a while. Now, it's time to start upgrading everyone else. As you can no
doubt understand, we're anxious to complete this process so we can spend
less time maintaining the old platform, and more time improving the new
one. However, we also want to be sure that you have plenty of time to check
out the new platform and have your concerns, if any, addressed.

We're going to start upgrading active projects starting on Monday, April
22, starting with the longest-inactive and moving forward. Since each
upgrade takes a different amount of time, depending on the size of the
repositories, mailing list archives, and so on, we can't tell for sure when
we'll get to your project.

If you're ready to go ahead and upgrade your project now, you can do that
at http://sf.net/p/upgrade/

If you have a specific concern about the upgrade, or need to delay the
upgrade of your project, due to a release or other project activity, please
get in touch NOW, at com...@so... so that we can work
something out.

--
SourceForge Community Team
com...@so...
http://sourceforge.net/

please help me !