From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: Zsh Hackers' List <zsh-workers@zsh.org>
Subject: Fw: zsh, it's time to upgrade your classic SourceForge project
Date: Tue, 15 Jan 2013 19:45:29 +0000 [thread overview]
Message-ID: <20130115194529.6855de7d@pws-pc.ntlworld.com> (raw)
Sourceforge is updating their system; for some reason this time round
it's not automatic. I shall probably just press the button, but beware
the URLs will changed (it's not as if that would be the first time).
Now is probably as good a time as any.
No, they're not retiring CVS yet.
pws
Dear zsh 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
rbowen@sourceforge.net
next reply other threads:[~2013-01-15 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 19:45 Peter Stephenson [this message]
2013-01-15 23:58 ` Phil Pennock
2013-01-17 19:55 ` Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130115194529.6855de7d@pws-pc.ntlworld.com \
--to=p.w.stephenson@ntlworld.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).