Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
From: Stuart Donaldson <stu@as...> - 2003-01-22 03:16:08
Just a heads-up for the developers out there that might have a change in
I am planning on putting 0.8b1 up on the web site later on this evening.
Also I have created a HomPage module in CVS which mirrors the home page
on SF. I plan to update the web site to be a checked-out copy of the
home page. This would allow us to publish by simply updating the
HomePage module, and then going to the shell server and doing a cvs update.
The CVS copy of the HomePage does not include the tarball's nor the
exploaded tarballs that contained documentation from the releases. But
it does contain the .zip, .exe, and .dll files for the adapters (with
the appropriate -kb option ;-).
A couple of questions:
Any reason we need to keep the old tarballs directly on the home
page, rather than linking to the SF download of the tarballs?
Any reason we should keep the old exploaded directories of all of
the older packages on the site as well? Seems like we should have the
current released version, and perhaps the beta version for access to