From: Maynard J. <may...@us...> - 2007-07-18 19:44:35
|
Update of /cvsroot/oprofile/oprofile-www In directory sc8-pr-cvs3.sourceforge.net:/tmp/cvs-serv13086 Modified Files: ChangeLog releasechecklist Log Message: Add detail to the checklist steps Index: ChangeLog =================================================================== RCS file: /cvsroot/oprofile/oprofile-www/ChangeLog,v retrieving revision 1.73 retrieving revision 1.74 diff -u -p -d -r1.73 -r1.74 --- ChangeLog 16 Jul 2007 18:25:32 -0000 1.73 +++ ChangeLog 18 Jul 2007 19:44:35 -0000 1.74 @@ -1,3 +1,8 @@ +2007-07-18 Maynard Johnson <may...@us...> + + * releasechecklist: Replace text file with an HTML + document containing detailed instructions. + 2007-07-16 Maynard Johnson <may...@us...> * download/index.php3: Index: releasechecklist =================================================================== RCS file: /cvsroot/oprofile/oprofile-www/releasechecklist,v retrieving revision 1.3 retrieving revision 1.4 diff -u -p -d -r1.3 -r1.4 --- releasechecklist 15 Jun 2007 13:27:01 -0000 1.3 +++ releasechecklist 18 Jul 2007 19:44:35 -0000 1.4 @@ -1,11 +1,322 @@ -# 1. change version to non-cvs and commit -# 2. make dist -# 3. upload to sf -# 4. add release -# 5. close fixed bugs -# 6. send release email -# 7. update freshmeat -# 8. cvs tag RELEASE_0_0_8 -# 9. update webpage release-notes/, news, download, srcdoc/, doc/ -# 10. sync website to oprofile-www CVS -# 11. change configure.in version to cvs and commit +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<html> +<head> + <meta content="text/html; charset=UTF-8" http-equiv="content-type"> + <title>OProfile release checklist</title> +</head> +<body> +<h1><a name="OProfile_release_checklist"></a>OProfile release checklist</h1> +<span style="font-weight: bold;"><br> +Note:</span> The OProfile maintainer must give you admin privileges to +put out a release.<br> +<br> +<ol> + <li> + <pre>Create/update Release Notes for new release</pre> + <ul> + <li>Any changelog entry that fixes a user-visible bug should be +in the notes unless it was not reproducible in the last release. +All new user-visible features should also be in the release notes.<br> + </li> + </ul> + </li> + <li> + <pre>Change version to non-cvs and commit</pre> + </li> + <ul> + <li>Change version in configure.in's AM_INIT_AUTOMAKE</li> + <li>Probably want to start with a +<<span style="font-style: italic;">v.r.m</span>>-rc<<span + style="font-style: italic;">n</span>>. Since this has to be +changed for +every release candidate, it's best not to commit this until the final +GA of the release.<br> + </li> + </ul> + <li> + <pre>make dist</pre> + </li> + <ul> + <li>If there are any ChangeLog-xxxx files that are not listed in +the EXTRA_DIST target in Makefile.am, add them to the list and <span + style="text-decoration: underline;">commit </span>this Makefile.am +change (commit this now, otherwise you'll be making the exact same +change for every release candidate.<br> + </li> + <li>./autogen.sh; ./configure; make dist. This produces a +tarball called oprofile-<<span style="font-style: italic;">release</span>>.tar.gz, +where "<span style="font-style: italic;">release</span>" is what +you specified in AM_INIT_AUTOMAKE.<br> + </li> + </ul> + <li> + <pre>upload the tar ball to sf</pre> + </li> + <ul> + <li>With a browser, go to OProfile website and click on the +"SOURCEFORGE.NET" at the bottom left of the screen. Sign in with +your admin user ID. Select "File Releases" from the +"Admin" drop-down tab. Click on the "Help" link under the "Admin" +tab; then go to the "Upload a file" section.</li> + <ul> + <li><span style="font-weight: bold;">Note</span>: For +convenience, the "<a href="#Upload_a_file">Upload a file</a>" section +of the Help documentation is included here.<br> + </li> + </ul> + </ul> + <li> + <pre>add release</pre> + </li> + <ul> + <li>With a browser, go to the OProfile website and click on the +"SOURCEFORGE.NET" at the bottom left of the screen. Sign in with +your admin user ID and password. Select "File Releases" from the +"Admin" drop-down tab. Click on the "Help" link under the "Admin" +tab; then go to the "Create or edit a release" section. <br> + </li> + <ul> + <li><span style="font-weight: bold;">Details: <br> + </span></li> + </ul> + <ol> + <ol> + <li><span style="font-weight: bold;"></span>Name the release +the same as what you specified in AM_INIT_AUTOMAKE in step 1; e.g +0.9.4-rc1.</li> + <li>For each successive release candidate and the final GA +release, edit the <<span style="font-style: italic;">v.r.m</span>>-rc<<span + style="font-style: italic;">n</span>> release instead of creating +new +ones. You can change the release name, remove old tar balls and +attach new ones.</li> + <li>Do <span + style="font-style: italic; text-decoration: underline;">not </span>check +the check-box for sending out a notice of the new file release until +the release is at the GA stage.<br> + </li> + <li>For release candidates, post a message to the oprofile-list +with a URL to the download page for the release you just created and +paste the Release Notes into the message.<br> + </li> + </ol> + </ol> + <ul> + <li><span style="font-weight: bold;">Note</span>: For +convenience, the "<a href="#Create_or_edit_a_release">Create or edit a +release</a>" section of the Help documentation is included here.<br> + <br> + </li> + </ul> + </ul> + <li>Get testing feedback from the community. Return to +step 1 for each new release candidate (and, eventually, for the +GA). The following steps are to be done once the decision is made +to GA and you've iterated over the previous steps again for the GA +release.<br> + </li> + <li> + <pre>close fixed bugs</pre> + </li> + <ul> + <li>Log into SourceForge with admin ID and close oprofile bugs that +have been +fixed in this release. <span style="font-weight: bold;">Note:</span> +Bugs for problems that are <span style="font-style: italic;">not</span> +reproducible in previous releases should +have been closed already.<br> + </li> + </ul> + <li> + <pre>update freshmeat</pre> + </li> + <ul> + <li>Create an account for yourself on freshmeat (<a + href="http://freshmeat.net/projects/oprofile">http://freshmeat.net/projects/oprofile</a>) +and have the OProfile maintainer give you developer permissions. +Log in and click on the "add release" URL and follow the bouncing +ball. If unsure about some of the fields, look at how previous +releases were specified.<br> + </li> + </ul> + <li> + <pre>Run the command 'cvs tag RELEASE_<v_r_m>'; e.g, 'cvs tag RELEASE_0_9_4'</pre> + </li> + <ul> + <li>After committing the change to configure.in's AM_INIT_AUTOMAKE +for the GA release, cd into the checked-out oprofile directory and run +the 'cvs tag' command. You should get a password prompt, then +you'll see a message for every file in the project: "T +<filename>". You can go to OProfile CVS on SourceForge and +browse the files to see that the new tag has been applied.<br> + </li> + </ul> + <li> + <pre>update web page release-notes/, news, download, srcdoc/, doc/</pre> + </li> + <ul> + <li>Do a normal cvs checkout of oprofile and +oprofile-www.</li> + <li>In oprofile-www, edit the news/index.php3 and +download/index.php3 +files to point to the new release. Also verify +correctness/completeness of the new release-notes. Do 'cvs +commit' of these changes. </li> + <li>In oprofile, do ./autogen.sh, ./configure, and then cd into +doc/ and run 'make chunk'. Tar up the doc/ directory. Then +cd into doc/srcdoc/ and run 'make'. Tar up the srcdoc/ directory.</li> + </ul> + <li> + <pre>sync website to oprofile-www CVS</pre> + </li> + <ul> + <li>ssh to oprofile.sf.net with your admin ID and go to oprofile's +www directory +(/home/groups/o/op/oprofile/htdocs/). There's a cvs dir there; 'cvs +update' that.</li> + <li>Unpack the new doc and srcdoc tar balls created in the previous +step.</li> + <li>Ensure that any new files you create have write access for the +'oprofile' group (do 'chmod g+w' if necessary).</li> + <li>Point your browser at http://oprofile.sourceforge.net/cvs/ and +verify the website, documentation, etc. looks OK.</li> + <li>Make a backup of the parent (htdocs) directory; then move all +the stuff from the cvs dir into the parent dir to make it live. +Now use your browser to verify that the actual OProfile website looks +OK.<br> + </li> + </ul> + <li> + <pre>send release email</pre> + </li> + <li> + <pre>change AM_INIT_AUTOMAKE in configure.in '<<span + style="font-style: italic;">v.r.m</span>>cvs' and commit</pre> + </li> +</ol> +<br> +<br> +=================================================================<br> +<h2>Appendix: Source Forge Help<br> +</h2> +<h3><a name="Upload_a_file"></a>Upload a file</h3> +<br> +The file upload process uses the FTP protocol only, SSH based protocols +are not used here (SFTP, SCP and rsync over SSH are not supported). +Should these instructions fail, upload the files to the project shell +server and then login to the project shell server and perform the +upload from that host.<br> +<br> +The directory listing of the /incoming directory will not be displayed +for security reasons. Files with duplicate names of other files in the +directory cannot be overwritten. Files that have been present in the +/incoming directory for more than 24 hours are automatically purged +from the system. No mechanism exists to remove files prior to the 24 +hour delay.<br> +<br> +Any modern operating system comes with a command-line FTP client, +instructions for use follows:<br> +<br> +<ol> + <li>Use FTP to connect to upload.sourceforge.net.</li> + <li>Login using 'anonymous' for the username and your email address +for the password.</li> + <li>Switch to binary mode (command: bin).</li> + <li>Switch to passive mode (command: passive), if non-passive mode +doesn't work.</li> + <li>Change local directory to the directory containing the files to +upload (command: lcd /PATH/TO/FILES).</li> + <li>Change remote directory to /incoming (command: cd /incoming).</li> + <li>Turn on upload status printing, if you want to watch the progress +(command: hash).</li> + <li>Upload the desired files for the release. Filenames may only +contain alphanumeric characters, periods, dashes or underscores +(command: put FILENAME).</li> + <li>Disconnect from the FTP server (command: quit).</li> +</ol> +<br> +Example FTP session:<br> +<br> +$ ftp upload.sourceforge.net<br> +Connected to osdn.dl.sourceforge.net.<br> +220-********************************************************************<br> +220- On This Site:<br> +220- +/incoming +SourceForge.net Project File Upload<br> +220- +*********************************************************************<br> +220-<br> +220<br> +530 Please login with USER and PASS.<br> +530 Please login with USER and PASS.<br> +KERBEROS_V4 rejected as an authentication type<br> +Name (upload.sourceforge.net): anonymous<br> +331 Please specify the password.<br> +Password:<br> +230 Login successful.<br> +Remote system type is UNIX.<br> +Using binary mode to transfer files.<br> +ftp> bin<br> +200 Switching to Binary mode.<br> +ftp> passive<br> +Passive mode on.<br> +ftp> hash<br> +Hash mark printing on (1024 bytes/hash mark).<br> +ftp> lcd /PATH/TO/FILES<br> +Local directory now /PATH/TO/FILES<br> +ftp> cd /incoming<br> +250 Directory successfully changed.<br> +ftp> put FILENAME<br> +local: FILENAME remote: FILENAME<br> +227 Entering Passive Mode (66,35,250,221,233,148)<br> +150 Ok to send data.<br> +###################################################################<br> +###################################################################<br> +###################################################################<br> +################################################<br> +226 File receive OK.<br> +255908 bytes sent in 4.6 seconds (54 Kbytes/s)<br> +ftp> quit<br> +<br> +<br> +<h3><a name="Create_or_edit_a_release"></a>Create or edit a release</h3> +Releases belong to a package. Generally, a release will contain all the +files relating to a software version. As an example, the project lame +wants to release version 1.0.0 of lame, they create a new release under +the package lame named 1.0.0. There are 2 different versions of lame +1.0.0, one for Windows and another for Linux. Both files uploaded are +associated with the same release as they have the same features and are +the same version.<br> +<br> +It may take an hour or so before the files released are available on +all mirrors. To ensure the file gets distributed, make sure the file is +not hidden during the release process or afterwards.<br> +<br> +To create a release:<br> +<br> +<ol> + <li>Login to the SourceForge.net website.</li> + <li>Select the project to administer from the 'My Projects' listing +on the My Page.</li> + <li>Select 'File Releases' from the Admin pulldown.</li> + <li>Click on the '[Add Release]' link next to the Package Name +associated with the release.</li> + <li>Enter the release name for the release into the 'New release +name:' field and click the 'Create This Release' button.</li> + <li>Type in or paste Change Log and Release notes for the release, if +desired. They must be in plain text format.</li> + <li>Check the checkbox next to the filename of each file to be added +to the release in section 2 of the form, and click on the 'Add Files +and/or Refresh View' button.</li> + <li>Go to Step 3 of the form, modifying the value in each field for +each file, as necessary. Click on the 'Update/Refresh' button after +each change to a file.</li> + <li>If you want to send out a notice of the new file release, go to +Step 4 in the form, check the 'I'm sure' checkbox and click the 'Send +Notice' button.</li> +</ol> +<br> +<br> +</body> +</html> |