[Gnuplot-py-svn] SF.net SVN: gnuplot-py:[321] trunk/RELEASES.txt

[<mh...@us...>]

Revision: 321
          http://gnuplot-py.svn.sourceforge.net/gnuplot-py/?rev=321&view=rev
Author:   mhagger
Date:     2011-11-19 14:51:37 +0000 (Sat, 19 Nov 2011)
Log Message:
-----------
Fix whitespace.

Modified Paths:
--------------
    trunk/RELEASES.txt

Modified: trunk/RELEASES.txt
===================================================================
--- trunk/RELEASES.txt	2011-11-19 14:51:22 UTC (rev 320)
+++ trunk/RELEASES.txt	2011-11-19 14:51:37 UTC (rev 321)
@@ -9,13 +9,13 @@
 1. Edit the following files for the release:
 
    NEWS.txt -- add the version number at the top of the file and make
-       sure that the comments are up to date. 
+       sure that the comments are up to date.
        Remove the "Version ?.?:" line.
 
    ANNOUNCE.txt -- add the version number at the top of the file and
        update the blurbs as appropriate.
 
-   Gnuplot.html -- update the version number where it appears.  
+   Gnuplot.html -- update the version number where it appears.
        Update the "News" section.
 
    __init__.py -- increment the __version__ string. If there is a
@@ -30,14 +30,14 @@
 
 4. Create new documentation using happydoc. cd to the Gnuplot directory, then
    $ rm -rf doc
-   $ cd .. 
+   $ cd ..
    $ happydoc -d Gnuplot/doc -t 'Gnuplot.py' Gnuplot
    Note:
    To install happydoc, you download its source from sourceforge,
-   and unpack it, then 
+   and unpack it, then
      $ cp -r happydoclib/ /usr/lib/python2.5/site-packages/
      $ cp happydoc /usr/local/bin
-   
+
 5. Generate the source distributions in Gnuplot/dist; cd to Gnuplot and then:
    $ python2 ./setup.py sdist --formats=gztar,zip
 
@@ -50,7 +50,7 @@
    $ cd dist
    $ ftp upload.sourceforge.net   (username anonymous)
      cd incoming
-     put gnuplot-py-1.8.tar.gz  
+     put gnuplot-py-1.8.tar.gz
      put gnuplot-py-1.8.zip
 
    a. Log in to the sourceforge web interface, choose Gnuplot.py
@@ -63,20 +63,20 @@
    d. Type a release name of the form "1.8".
 
       Click on "Create This Release"
-      
+
    e. In "Step 1: Edit Existing Release",
       check the "Preserve my pre-formatted text." button below the text boxes
       Paste the "New features in this version" section of ANNOUNCE.txt
       into the "Paste the notes in" text box.
-      Paste the section of NEWS.txt for this release in to the 
+      Paste the section of NEWS.txt for this release in to the
       "Paste The Change Log In" text box
       Click "Submit/refresh"
 
    f. In "Step 2: Add Files To This Release" section,
-      Select gnuplot-py-1.8.tar.gz  and gnuplot-py-1.8.zip in the 
+      Select gnuplot-py-1.8.tar.gz  and gnuplot-py-1.8.zip in the
       list of files, then click   "Add files or refresh view"
 
-   g. In "Step 3: Edit Files In This Release", 
+   g. In "Step 3: Edit Files In This Release",
       For gnuplot-py-1.8.tar.gz, under "Processor" select
       "Platform-Independent" and under "file type" select "source .gz",
       then click "Update/refresh"
@@ -95,7 +95,7 @@
      put NEWS.txt
      quit
    This updates the Gnuplot.html home page, http://gnuplot-py.sourceforge.net/
-     
+
 9. Update the project news page (http://sourceforge.net/projects/gnuplot-py/)
    - log in to sourceforge on the web
    - select Gnuplot.py from "My projects"
@@ -107,7 +107,7 @@
           Highlights:
           + Compatible with NumPy
           + Compatible with future python where "with" will be a reserved word
-          + Added a 'pdf' terminal definition 
+          + Added a 'pdf' terminal definition
           + hardcopy allows for terminal='svg'
           See NEWS.txt for more details.
           ----
@@ -122,7 +122,6 @@
 12. Append a '+' to the __version__ string in __init__.py to
     distinguish intermediate Subversion releases from official
     releases.  Add a "Version ?.?:" line to NEWS.txt to receive future
-    change notes.  
-    Check the changes into Subversion, with a suitable comment, eg:
-    svn commit  -m "Version 1.8+"
+    change notes.  Check the changes into Subversion, with a suitable
+    comment.
 

This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.