[prev in list] [next in list] [prev in thread] [next in thread]
List: squirrelmail-cvs
Subject: [SM-CVS] SF.net SVN: squirrelmail:[13925]
From: pdontthink () users ! sourceforge ! net
Date: 2010-03-07 2:30:24
Message-ID: E1No6G8-0003CS-P4 () sfp-svn-3 ! v30 ! ch3 ! sourceforge ! com
[Download RAW message or body]
Revision: 13925
http://squirrelmail.svn.sourceforge.net/squirrelmail/?rev=13925&view=rev
Author: pdontthink
Date: 2010-03-07 02:30:13 +0000 (Sun, 07 Mar 2010)
Log Message:
-----------
sf.net admin section is obsolete
Modified Paths:
--------------
trunk/documentation/devel/devel.sgml
Modified: trunk/documentation/devel/devel.sgml
===================================================================
--- trunk/documentation/devel/devel.sgml 2010-03-07 02:08:57 UTC (rev 13924)
+++ trunk/documentation/devel/devel.sgml 2010-03-07 02:30:13 UTC (rev 13925)
@@ -2958,13 +2958,13 @@
<enum>
<item><tt>gpg --verify squirrelmail-X.Y.Z.tar.gz.sig \
squirrelmail-X.Y.Z.tar.gz</tt> </enum>
- <item> Upload your GPG signatures to Sourceforge.net. See the next \
(optional) step or see <url \
url="http://apps.sourceforge.net/trac/sourceforge/wiki/Release%20files%20for%20download#Uploadafile" \
name="sf.net instructions"> or see <url \
url="http://apps.sourceforge.net/trac/sourceforge/wiki/File%20management%20service" \
name="sf.net upload protocols">.
- <item> The make-release script's upload feature is dated and is currently \
commented out. SourceForge has made changes to their file management and release \
system more than once recently, not without much frustration for us. The following \
steps are how version 1.4.20 was uploaded in March, 2010. + <item> Upload \
your GPG signatures to Sourceforge.net. See the next step or see <url \
url="http://apps.sourceforge.net/trac/sourceforge/wiki/Release%20files%20for%20download#Uploadafile" \
name="sf.net instructions"> or see <url \
url="http://apps.sourceforge.net/trac/sourceforge/wiki/File%20management%20service" \
name="sf.net upload protocols">. + <item> The make-release script's upload \
feature is dated and is currently commented out (even if you get that to work, you \
still need to upload your GPG signatures and use the instructions below to set the \
release file properties, etc.). SourceForge has made changes to their file \
management and release system more than once recently, not without much frustration \
for us. The following steps are how version 1.4.20 was uploaded in March, 2010. \
<enum>
<item>Since when logged in by sftp, creating directories seems to \
fail
with a permission denied (sigh), first create the release \
directory ahead of time by using web interface at:
- <tscreen><url \
url="http://apps.sourceforge.net/trac/sourceforge/wiki/File%20management%20service" \
name="https://sourceforge.net/project/admin/explorer.php?group_id=311"></tscreen> + \
<tscreen><url url="https://sourceforge.net/project/admin/explorer.php?group_id=311" \
name="https://sourceforge.net/project/admin/explorer.php?group_id=311"></tscreen>
For example, click to expand the "stable" directory and then
click on the "gear" icon next to the "stable" directory and
select to create a new folder, naming it with the release \
version @@ -2985,7 +2985,7 @@
</verb></tscreen>
<item>Now you have to use the web interface to assign properties to \
the uploaded files:
- <tscreen><url \
url="http://apps.sourceforge.net/trac/sourceforge/wiki/File%20management%20service" \
name="https://sourceforge.net/project/admin/explorer.php?group_id=311"></tscreen> + \
<tscreen><url url="https://sourceforge.net/project/admin/explorer.php?group_id=311" \
name="https://sourceforge.net/project/admin/explorer.php?group_id=311"></tscreen> \
<enum>
<item>Navigate to the new release folder (e.g., stable ==> \
1.4.20).
<item>Click on the ReleaseNotes file and tick the Release
@@ -3013,32 +3013,6 @@
<tscreen>svn copy doc/ReleaseNotes \
doc/release_notes_archive/X.Y/Notes-X.Y.Z.txt</tscreen>
<item> Commit all these changes to SVN with a note saying that it is ready \
for continued development. </enum>
-<item><bf/sf.net admin stuff:/ Post the release files on SourceForge (you need to be \
a "release technician" to do this)
- <enum>
- <item> Create the new release of files
- <enum>
- <item> Log into SourceForge and go to the SquirrelMail project page.
- <item> Under the "Project Admin" menu, select "Feature Settings".
- <item> Now click the "Manage" link to the right of "File Release \
System".
- <item> Click "Add Release" for the correct package.
- <item> Enter the release name in X.Y.Z format (no SquirrelMail or \
anything, just X.Y.Z) and click the "Create This Release" button.
- <item> The next page it shows you will be the same page you get to if \
you clicked on "edit release" from the "Edit/Release Files" page earlier and selected \
a release name.
- </enum>
- <item> Enter the ChangeLog (only the part of that file for this release, \
not the whole file) and ReleaseNotes (the whole file) for this SourceForge file \
release.
- <item> Add the newly uploaded files to the release
- <enum>
- <item> Go down to the "add files to this release" section
- <item> Select the files you recently uploaded (be nice and leave \
other peoples files alone).
- <item> Click the "Add Files and/or Refresh View" button.
- </enum>
- <item> For each files added (tar.gz, tar.bz2, and zip), one at a time, set \
the file info correctly.
- <enum>
- <item> Set the processor to 'Platform-Independent'.
- <item> Set the file type (.bz2 for the tar.bz2 file, .gz for the \
tar.gz file, .zip for the zip file, and .rpm for the .rpm files).
- <item> Click the "Update/Refresh" button for that file.
- </enum>
- <item> Annouce the file release to those monitoring it with the button on \
the bottom of the page.
- </enum>
<item><bf/Enable downloading:/ Update the download page for the SquirrelMail \
website. <enum>
<item> SSH into sciurida
This was sent by the SourceForge.net collaborative development platform, the world's \
largest Open Source development site.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
-----
squirrelmail-cvs mailing list
List address: squirrelmail-cvs@lists.sourceforge.net
List info (subscribe/unsubscribe/change options): \
https://lists.sourceforge.net/lists/listinfo/squirrelmail-cvs
Repository: http://squirrelmail.org/svn
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic