newgem 0.10.1 → 0.10.2

data/History.txt

@@ -1,3 +1,13 @@
+== 0.10.2 2007-05-25
+
+* 3 major enhancements
+  * Generated Rakefile only attempts to discover username from ~/.rubyforge/user-config.yml when its required [thx Jeroen Janssen]
+  * Helpful error message produced if 'rubyforge setup' never run
+  * Fixed the REV algorithm for subversion [thx Robert Berger]
+* 2 minor enhancement
+  * Copied index.txt into README.txt - it looks crap, but at least there is content
+  * Generated Rakefile was missing a \
+
 == 0.10.1 2007-05-24
 
 * 4 minor enhancements
@@ -60,15 +70,15 @@
 
 == 0.8.1 
 
-  - Generated test file's class name now prefixed with Test, instead of suffixed
+* Generated test file's class name now prefixed with Test, instead of suffixed
 
 == 0.8.0 
 
-  - Uses hoe itself - less hypocritical
-	- Generated test files use name 'test_<gemname>.rb' instead of '<gemname>_test.rb' to support
-	  ZenTest's autotest expectations of naming. Manifest updated too.
+* Uses hoe itself - less hypocritical
+* Generated test files use name 'test_<gemname>.rb' instead of '<gemname>_test.rb' to support
+* ZenTest's autotest expectations of naming. Manifest updated too.
 
 == 0.7.1 
 
-  - Installed gems now don't require 'hoe' (based on comments at  http://blog.evanweaver.com/articles/2007/01/10/if-you-dont-want-to-hoe-echoe)
+* Installed gems now don't require 'hoe' (based on comments at http://blog.evanweaver.com/articles/2007/01/10/if-you-dont-want-to-hoe-echoe)
 

data/README.txt

@@ -1,3 +1,193 @@
-README for newgem
-=================
+h1. New Gem Generator
 
+h1. → 'newgem'
+
+h2. What
+
+Quickly bundle any Ruby libraries into a RubyGem and share it with the world, your colleagues, or perhaps just with yourself amongst your projects.
+
+RubyGems are centrally stored, versioned, and support dependencies between other gems, so they are the ultimate way to bundle libraries, executables, associated tests, examples, and more.
+
+Within this gem, you get one thing - <code>newgem</code> - an executable to create your own gems. Your new gems will include designated folders for Ruby code, test files, executables, and even a default website page for you to explain your project, and which instantly uploads to RubyForge website (which looks just like this one by default)
+
+h2. Installing
+
+The <code>newgem</code> application is distributed itself as a RubyGem and is available immediately after installation.
+
+<pre syntax="ruby">sudo gem install newgem</pre>
+
+Alternately, download the gem and install manually.
+
+h2. The basics
+
+Go to the folder where you want to create your new gem folder structure, and run the <code>newgem</code> command to generate your gem scaffolding.
+
+<pre>$ cd ~/ruby_projects
+$ newgem wizzo
+creating: wizzo
+creating: wizzo/CHANGELOG.txt
+creating: wizzo/README.txt
+creating: wizzo/lib
+creating: wizzo/scripts
+creating: wizzo/website
+creating: wizzo/website/javascripts
+creating: wizzo/website/stylesheets
+creating: wizzo/lib/wizzo
+creating: wizzo/lib/wizzo.rb
+creating: wizzo/lib/wizzo/version.rb
+creating: wizzo/bin
+creating: wizzo/test
+creating: wizzo/test/test_helper.rb
+creating: wizzo/test/test_wizzo.rb
+creating: wizzo/examples
+creating: wizzo/setup.rb
+creating: wizzo/Rakefile
+creating: wizzo/Manifest.txt
+creating: wizzo/History.txt
+creating: wizzo/scripts/txt2html
+creating: wizzo/website/index.txt
+creating: wizzo/website/template.rhtml
+copying: wizzo/website/javascripts/rounded_corners_lite.inc.js
+copying: wizzo/website/stylesheets/screen.css
+NOW - update wizzo/Rakefile with gem description, etc
+</pre>
+
+As of 0.10.0 - you can generate test::unit or rspec test stubs via the -t, --test-with options
+
+h3. Setup
+
+Now modify the constants at the top of *Rakefile*, with your name, email and the location where you'll host your website for the gem. The defaults are tied to RubyForge for uploading the gems and the website (see below).
+
+h3. Create code and tests
+
+Then create your libraries (files in <code>lib</code>) and your tests (files in <code>test</code> that look like <code>test_TESTNAME.rb</code>). John Grey III did a nice video on test-driven design, that's worth watching if TDD is new to you.
+
+If you create any new files, you need to manually add them to the Manifest.txt. Alphabetical order is optional, but it will make the results of <code>rake check_manifest</code> look clean if you keep them ordered. If a file is not in the Manifest.txt it will not be included in the gem when you package and release it.
+
+h3. Executables
+
+You can include executable Ruby applications in your gem, which will be accessible on Windows and Unix/Linux/MacOS, by creating scripts in the <code>bin</code> folder. When the gem is deployed by users, these executables will be automatically placed within their path.
+
+h3. Website
+
+The final step before releasing your gem to the world is the all-important website. Edit the file <code>website/index.txt</code> using Textile/Redcloth syntax. Syntax highlighting is also supported (see below). If you need more website pages, create more *txt* files in the website folder. 
+
+Run the rake task <code>rake website_generate</code> to convert all your website txt files into html files.
+
+NOTE: Currently, the initial <code>index.txt</code> file includes my details not yours. Currently you need to change this manually.
+
+If you don't want a website, remove the <code>website</code> related files from the Manifest.txt. 
+
+h3. Change the gems version number
+
+The version number is set in the file <code>lib/#gem name#/version.rb</code>. Update it as appropriate with major, minor and bug fix numbers. This value will be used when generating your website, for example.
+
+h3. Check the manifest
+
+<blockquote>Manifest: a customs document listing the contents put on a ship or plane.</blockquote>
+<cite>"Google - define:manifest":http://www.google.com/search?q=define%3Amanifest</cite>
+
+Similarly here, a manifest is the log of the files to be packaged into a gem. If its not in the <code>Manifest.txt</code> file, the users won't get it.
+
+Before you package your gem, you can compared the list of files in your gem folder, with the Manifest.txt:
+
+<pre>rake check_manifest</pre>
+
+The results show a _diff_ of the two.
+
+h2. Package and test locally
+
+Before releasing a new version of a gem, it is a great idea to install the gem locally and do some sanity checks. You know, to limit the chance of you looking like a noob.
+
+<pre>rake local_deploy</pre>
+
+This generates the website html files into your website folder, and locally installs the gem, ready for testing and local use.
+
+Now pretend to be a user, and do some tests - especially of new functionality - so you are comfortable all the files have been packaged up, and you haven't missed anything in the <code>Manifest.txt</code>.
+
+One set of tests you should do is to repeat any tutorials you include in your website. If your gem is dependent on other gems that are rapidly changing, its possible your tutorial might be invalid even if your unit tests are successful. Best you find any errors before the users start emailing you!
+
+h2. Releasing your gem to the world
+
+Once you're ready for release there are some final steps. 
+
+<a name="setup_rubyforge"></a>
+	
+
+h3. Setup your environment to upload to RubyForge.
+
+There are several steps you need to perform initially to "setup your environment for uploading gems to RubyForge":rubyforge.html.
+
+
+h3. Document changes in History.txt
+
+Between each version of your gem, you probably changed something. You should document this in the <code>History.txt</code> file. For each new release, you need to add two paragraphs that look like this:
+
+<pre>== 0.5.4 14/4/2007
+	
+* 1 major improvement
+  * 150% more Wizzos
+* 2 bug fixes
+  * Wizzos are the proper colour
+  * You only get Wizzos when you ask for them
+</pre>
+
+The two paragraphs will be automatically picked up by the following release process and documented against the release on RubyForge site. To see an example of the end result, look at the "*Changes* section for hoe 1.2":http://rubyforge.org/frs/shownotes.php?release_id=9695.
+
+The History.txt notes for your first release have already been started for you.
+
+
+h3. Release the gem and upload the website and rdocs
+
+Run <code>rake deploy VERSION=X.Y.Z</code> after you've done all these steps. It does the following:
+
+# Uploads your website to rubyforge
+# Uploads your rdocs to rubyforge
+# Packages and uploads your gem to RubyForge
+
+It can take an hour or two before new gem releases are available via the gem installer. But when they are ready, everyone will be able to download and install your gem using:
+
+<pre>sudo gem install #gem_name#</pre>
+
+If your GEM_NAME and RUBYFORGE_PROJECT name are the same, then:
+
+* http://RUBYFORGE_PROJECT.rubyforge.org is your website, and
+* http://RUBYFORGE_PROJECT.rubyforge.org/rdoc is your rdocs
+
+If they are different, then:
+
+* http://RUBYFORGE_PROJECT.rubyforge.org/GEM_NAME is your website, and
+* http://RUBYFORGE_PROJECT.rubyforge.org/GEM_NAME/rdoc is your rdocs
+
+h2. Bonus tasks thanks to Hoe
+
+Your gem uses the Hoe gem to provide a dozen or so useful rake tasks for managing your gem, such as <code>release</code>, <code>check_manifest</code> and <code>publish_docs</code>.
+
+See them all with:
+
+<pre>rake -T</pre>
+
+Remember, the Rakefile is yours to extend as you please with more rake tasks, such as the <code>website</code> tasks which are already added.
+
+For more information about each task, see the "Hoe README":http://seattlerb.rubyforge.org/hoe/
+
+h2. Related articles
+
+* "Original blog article and tutorial":http://drnicwilliams.com/2006/10/11/generating-new-gems/
+
+h2. Dr Nic's Blog
+
+"http://www.drnicwilliams.com":http://www.drnicwilliams.com - for future announcements and
+other stories and things.
+
+h2. Forum
+
+"http://groups.google.com/group/new-gem-generator":http://groups.google.com/group/new-gem-generator
+
+h2. License
+
+This code is free to use under the terms of the MIT license. 
+
+h2. Contact
+
+Comments are welcome. Send an email to "Dr Nic Williams":mailto:drnicwilliams@gmail.com.

data/Rakefile

@@ -22,6 +22,7 @@ HOMEPATH = "http://#{RUBYFORGE_PROJECT}.rubyforge.org"
 DOWNLOAD_PATH = "http://rubyforge.org/projects/#{RUBYFORGE_PROJECT}"
 
 REV = nil #File.read(".svn/entries")[/committed-rev="(\d+)"/, 1] rescue nil
+# REV = `svn info`.each {|line| if line =~ /^Revision:/ then k,v = line.split(': '); break v.chomp; else next; end} rescue nil
 VERS = Newgem::VERSION::STRING + (REV ? ".#{REV}" : "")
 CLEAN.include ['**/.*.sw?', '*.gem', '.config', '**/.DS_Store']
 RDOC_OPTS = ['--quiet', '--title', "newgem documentation",
@@ -52,9 +53,9 @@ hoe = Hoe.new(GEM_NAME, VERS) do |p|
   #p.spec_extras    - A hash of extra values to set in the gemspec.
 end
 
-CHANGES = hoe.paragraphs_of('History.txt', 0..1).join("\\n\\n")
+CHANGES = hoe.paragraphs_of('History.txt', 0..1).join("\n\n")
 PATH    = (RUBYFORGE_PROJECT == GEM_NAME) ? RUBYFORGE_PROJECT : "\#{RUBYFORGE_PROJECT}/\#{GEM_NAME}"
-hoe.remote_rdoc_dir = File.join(PATH.gsub(/^#{RUBYFORGE_PROJECT}/,''), 'rdoc')
+hoe.remote_rdoc_dir = File.join(PATH.gsub(/^#{RUBYFORGE_PROJECT}\/?/,''), 'rdoc')
 
 desc 'Generate website files'
 task :website_generate => :load_consts do

data/lib/newgem.rb

@@ -3,3 +3,5 @@ end
 
 require 'newgem/rubyforge'
 require 'newgem/version'
+
+

data/lib/newgem/version.rb

@@ -2,7 +2,7 @@ module Newgem #:nodoc:
   module VERSION #:nodoc:
     MAJOR = 0
     MINOR = 10
-    TINY  = 1
+    TINY  = 2
 
     STRING = [MAJOR, MINOR, TINY].join('.')
   end

data/templates/Rakefile

@@ -16,14 +16,33 @@ AUTHOR = '#{author}'  # can also be an array of Authors
 EMAIL = "#{email}"
 DESCRIPTION = "description of gem"
 GEM_NAME = '#{gem_name}' # what ppl will type to install your gem
-config = YAML.load(File.read(File.expand_path("~/.rubyforge/user-config.yml")))
-RUBYFORGE_USERNAME = config["username"]
+
+@config_file = "~/.rubyforge/user-config.yml"
+@config = nil
+def rubyforge_username
+  unless @config
+    begin
+      @config = YAML.load(File.read(File.expand_path(@config_file)))
+    rescue
+      puts <<-EOS
+ERROR: No rubyforge config file found: \#{@config_file}"
+Run 'rubyforge setup' to prepare your env for access to Rubyforge
+ - See http://newgem.rubyforge.org/rubyforge.html for more details
+      EOS
+      exit
+    end
+  end
+  @rubyforge_username ||= @config["username"]
+end
+
 RUBYFORGE_PROJECT = '#{gem_name}' # The unix name for your project
 HOMEPATH = "http://\#{RUBYFORGE_PROJECT}.rubyforge.org"
 DOWNLOAD_PATH = "http://rubyforge.org/projects/\#{RUBYFORGE_PROJECT}"
 
 NAME = "#{gem_name}"
-REV = nil # UNCOMMENT IF REQUIRED: File.read(".svn/entries")[/committed-rev="(\d+)"/, 1] rescue nil
+REV = nil 
+# UNCOMMENT IF REQUIRED: 
+# REV = `svn info`.each {|line| if line =~ /^Revision:/ then k,v = line.split(': '); break v.chomp; else next; end} rescue nil
 VERS = #{module_name}::VERSION::STRING + (REV ? ".\#{REV}" : "")
 CLEAN.include ['**/.*.sw?', '*.gem', '.config', '**/.DS_Store']
 RDOC_OPTS = ['--quiet', '--title', '#{gem_name} documentation',
@@ -58,7 +77,7 @@ end
 
 CHANGES = hoe.paragraphs_of('History.txt', 0..1).join("\\n\\n")
 PATH    = (RUBYFORGE_PROJECT == GEM_NAME) ? RUBYFORGE_PROJECT : "\#{RUBYFORGE_PROJECT}/\#{GEM_NAME}"
-hoe.remote_rdoc_dir = File.join(PATH.gsub(/^\#{RUBYFORGE_PROJECT}/,''), 'rdoc')
+hoe.remote_rdoc_dir = File.join(PATH.gsub(/^\#{RUBYFORGE_PROJECT}\\/?/,''), 'rdoc')
 
 desc 'Generate website files'
 task :website_generate do
@@ -69,8 +88,7 @@ end
 
 desc 'Upload website files to rubyforge'
 task :website_upload do
-  config = YAML.load(File.read(File.expand_path("~/.rubyforge/user-config.yml")))
-  host = "\#{config["username"]}@rubyforge.org"
+  host = "\#{rubyforge_username}@rubyforge.org"
   remote_dir = "/var/www/gforge-projects/\#{PATH}/"
   local_dir = 'website'
   sh %{rsync -av \#{local_dir}/ \#{host}:\#{remote_dir}}
@@ -82,8 +100,8 @@ task :website => [:website_generate, :website_upload]
 desc 'Release the website and new gem version'
 task :deploy => [:check_version, :website, :release] do
   puts "Remember to create SVN tag:"
-  puts "svn copy svn+ssh://\#{RUBYFORGE_USERNAME}@rubyforge.org/var/svn/\#{PATH}/trunk " +
-    "svn+ssh://\#{RUBYFORGE_USERNAME}@rubyforge.org/var/svn/\#{PATH}/tags/REL-\#{VERS} "
+  puts "svn copy svn+ssh://\#{rubyforge_username}@rubyforge.org/var/svn/\#{PATH}/trunk " +
+    "svn+ssh://\#{rubyforge_username}@rubyforge.org/var/svn/\#{PATH}/tags/REL-\#{VERS} "
   puts "Suggested comment:"
   puts "Tagging release \#{CHANGES}"
 end

data/test/test_svn.rb

@@ -0,0 +1,13 @@
+require File.dirname(__FILE__) + '/test_helper.rb'
+require 'newgem/svn'
+require 'mocha'
+
+class NewgemSvnTest < Test::Unit::TestCase
+
+  def setup
+  end
+  
+  def test_truth
+    assert true
+  end
+end

data/website/index.html

@@ -33,7 +33,7 @@
     <h1>New Gem Generator</h1>
     <div id="version" class="clickable" onclick='document.location = "http://rubyforge.org/projects/newgem"; return false'>
       Get Version
-      <a href="http://rubyforge.org/projects/newgem" class="numbers">0.10.1</a>
+      <a href="http://rubyforge.org/projects/newgem" class="numbers">0.10.2</a>
     </div>
     <h1>&#x2192; &#8216;newgem&#8217;</h1>
 
@@ -137,17 +137,6 @@ NOW - update wizzo/Rakefile with gem description, etc
 	<p>If you don&#8217;t want a website, remove the <code>website</code> related files from the Manifest.txt.</p>
 
 
-	<h2>Package and test locally</h2>
-
-
-	<p>Before releasing a new version of a gem, it is a great idea to install the gem locally and do some sanity checks. You know, to limit the chance of you looking like a noob.</p>
-
-
-<pre>rake local_deploy</pre>
-
-	<p>This generates the website into your website folder, and locally installs the gem, ready for testing and local use.</p>
-
-
 	<h3>Change the gems version number</h3>
 
 
@@ -171,12 +160,15 @@ NOW - update wizzo/Rakefile with gem description, etc
 	<p>The results show a <em>diff</em> of the two.</p>
 
 
-	<h3>Installation</h3>
+	<h2>Package and test locally</h2>
 
 
-<pre>rake install_gem</pre>
+	<p>Before releasing a new version of a gem, it is a great idea to install the gem locally and do some sanity checks. You know, to limit the chance of you looking like a noob.</p>
+
 
-	<p>This will repackage your code as a gem and install it as a local gem with the new version number.</p>
+<pre>rake local_deploy</pre>
+
+	<p>This generates the website html files into your website folder, and locally installs the gem, ready for testing and local use.</p>
 
 
 	<p>Now pretend to be a user, and do some tests &#8211; especially of new functionality &#8211; so you are comfortable all the files have been packaged up, and you haven&#8217;t missed anything in the <code>Manifest.txt</code>.</p>
@@ -206,13 +198,13 @@ NOW - update wizzo/Rakefile with gem description, etc
 	<p>Between each version of your gem, you probably changed something. You should document this in the <code>History.txt</code> file. For each new release, you need to add two paragraphs that look like this:</p>
 
 
-<pre>+++ 0.5.4 14/4/2007
+<pre>== 0.5.4 14/4/2007
 
-+ 1 major improvement
-    + 150% more Wizzos
-+ 2 bug fixes
-    + Wizzos are the proper colour
-    + You only get Wizzos when you ask for them
+* 1 major improvement
+  * 150% more Wizzos
+* 2 bug fixes
+  * Wizzos are the proper colour
+  * You only get Wizzos when you ask for them
 </pre>
 
 	<p>The two paragraphs will be automatically picked up by the following release process and documented against the release on RubyForge site. To see an example of the end result, look at the <a href="http://rubyforge.org/frs/shownotes.php?release_id=9695"><strong>Changes</strong> section for hoe 1.2</a>.</p>
@@ -221,30 +213,46 @@ NOW - update wizzo/Rakefile with gem description, etc
 	<p>The History.txt notes for your first release have already been started for you.</p>
 
 
-	<h3>Generate and upload the website</h3>
+	<h3>Release the gem and upload the website and rdocs</h3>
 
 
-	<p>The rake task <code>rake website_upload</code> will upload the website into a RubyForge project.</p>
+	<p>Run <code>rake deploy VERSION=X.Y.Z</code> after you&#8217;ve done all these steps. It does the following:</p>
 
 
-	<p>Or use the task <code>rake website</code>, which performs both the generation and the upload.</p>
+	<ol>
+	<li>Uploads your website to rubyforge</li>
+		<li>Uploads your rdocs to rubyforge</li>
+		<li>Packages and uploads your gem to RubyForge</li>
+	</ol>
 
 
-	<h3>Release the gem</h3>
+	<p>It can take an hour or two before new gem releases are available via the gem installer. But when they are ready, everyone will be able to download and install your gem using:</p>
 
 
-	<p>Run <code>rake deploy VERSION=X.Y.Z</code> after you&#8217;ve done all these steps, and your gem will be repackaged and released to RubyForge, <span class="caps">PLUS</span> your website will be released with the latest version number.</p>
+<pre>sudo gem install #gem_name#</pre>
 
+	<p>If your <span class="caps">GEM</span>_NAME and <span class="caps">RUBYFORGE</span>_PROJECT name are the same, then:</p>
 
-	<p>It can take an hour or two before new gem releases are available via the gem installer. But when they are ready, everyone will be able to download and install your gem using:</p>
 
+	<ul>
+	<li>http://RUBYFORGE_PROJECT.rubyforge.org is your website, and</li>
+		<li>http://RUBYFORGE_PROJECT.rubyforge.org/rdoc is your rdocs</li>
+	</ul>
+
+
+	<p>If they are different, then:</p>
+
+
+	<ul>
+	<li>http://RUBYFORGE_PROJECT.rubyforge.org/GEM_NAME is your website, and</li>
+		<li>http://RUBYFORGE_PROJECT.rubyforge.org/GEM_NAME/rdoc is your rdocs</li>
+	</ul>
 
-<pre>sudo gem install #gem_name#</pre>
 
 	<h2>Bonus tasks thanks to Hoe</h2>
 
 
-	<p>Your gem uses the Hoe gem to provide a dozen or so useful rake tasks for managing your gem, such as <code>release</code>.</p>
+	<p>Your gem uses the Hoe gem to provide a dozen or so useful rake tasks for managing your gem, such as <code>release</code>, <code>check_manifest</code> and <code>publish_docs</code>.</p>
 
 
 	<p>See them all with:</p>
@@ -252,7 +260,7 @@ NOW - update wizzo/Rakefile with gem description, etc
 
 <pre>rake -T</pre>
 
-	<p>Remember, the Rakefile is yours to extend as you please with more rake tasks, such as the <code>website</code> tasks already added.</p>
+	<p>Remember, the Rakefile is yours to extend as you please with more rake tasks, such as the <code>website</code> tasks which are already added.</p>
 
 
 	<p>For more information about each task, see the <a href="http://seattlerb.rubyforge.org/hoe/">Hoe <span class="caps">README</span></a></p>
@@ -290,7 +298,7 @@ other stories and things.</p>
 
 	<p>Comments are welcome. Send an email to <a href="mailto:drnicwilliams@gmail.com">Dr Nic Williams</a>.</p>
     <p class="coda">
-      <a href="mailto:drnicwilliams@gmail.com">Dr Nic</a>, 20th May 2007<br>
+      <a href="mailto:drnicwilliams@gmail.com">Dr Nic</a>, 24th May 2007<br>
       Theme extended from <a href="http://rb2js.rubyforge.org/">Paul Battley</a>
     </p>
 </div>

data/website/index.txt

@@ -78,14 +78,6 @@ NOTE: Currently, the initial <code>index.txt</code> file includes my details not
 
 If you don't want a website, remove the <code>website</code> related files from the Manifest.txt. 
 
-h2. Package and test locally
-
-Before releasing a new version of a gem, it is a great idea to install the gem locally and do some sanity checks. You know, to limit the chance of you looking like a noob.
-
-<pre>rake local_deploy</pre>
-
-This generates the website into your website folder, and locally installs the gem, ready for testing and local use.
-
 h3. Change the gems version number
 
 The version number is set in the file <code>lib/#gem name#/version.rb</code>. Update it as appropriate with major, minor and bug fix numbers. This value will be used when generating your website, for example.
@@ -103,11 +95,13 @@ Before you package your gem, you can compared the list of files in your gem fold
 
 The results show a _diff_ of the two.
 
-h3. Installation
+h2. Package and test locally
+
+Before releasing a new version of a gem, it is a great idea to install the gem locally and do some sanity checks. You know, to limit the chance of you looking like a noob.
 
-<pre>rake install_gem</pre>
+<pre>rake local_deploy</pre>
 
-This will repackage your code as a gem and install it as a local gem with the new version number.
+This generates the website html files into your website folder, and locally installs the gem, ready for testing and local use.
 
 Now pretend to be a user, and do some tests - especially of new functionality - so you are comfortable all the files have been packaged up, and you haven't missed anything in the <code>Manifest.txt</code>.
 
@@ -129,42 +123,51 @@ h3. Document changes in History.txt
 
 Between each version of your gem, you probably changed something. You should document this in the <code>History.txt</code> file. For each new release, you need to add two paragraphs that look like this:
 
-<pre>+++ 0.5.4 14/4/2007
+<pre>== 0.5.4 14/4/2007
 	
-+ 1 major improvement
-    + 150% more Wizzos
-+ 2 bug fixes
-    + Wizzos are the proper colour
-    + You only get Wizzos when you ask for them
+* 1 major improvement
+  * 150% more Wizzos
+* 2 bug fixes
+  * Wizzos are the proper colour
+  * You only get Wizzos when you ask for them
 </pre>
 
 The two paragraphs will be automatically picked up by the following release process and documented against the release on RubyForge site. To see an example of the end result, look at the "*Changes* section for hoe 1.2":http://rubyforge.org/frs/shownotes.php?release_id=9695.
 
 The History.txt notes for your first release have already been started for you.
 
-h3. Generate and upload the website
-
-The rake task <code>rake website_upload</code> will upload the website into a RubyForge project. 
 
-Or use the task <code>rake website</code>, which performs both the generation and the upload.
+h3. Release the gem and upload the website and rdocs
 
-h3. Release the gem
+Run <code>rake deploy VERSION=X.Y.Z</code> after you've done all these steps. It does the following:
 
-Run <code>rake deploy VERSION=X.Y.Z</code> after you've done all these steps, and your gem will be repackaged and released to RubyForge, PLUS your website will be released with the latest version number.
+# Uploads your website to rubyforge
+# Uploads your rdocs to rubyforge
+# Packages and uploads your gem to RubyForge
 
 It can take an hour or two before new gem releases are available via the gem installer. But when they are ready, everyone will be able to download and install your gem using:
 
 <pre>sudo gem install #gem_name#</pre>
 
+If your GEM_NAME and RUBYFORGE_PROJECT name are the same, then:
+
+* http://RUBYFORGE_PROJECT.rubyforge.org is your website, and
+* http://RUBYFORGE_PROJECT.rubyforge.org/rdoc is your rdocs
+
+If they are different, then:
+
+* http://RUBYFORGE_PROJECT.rubyforge.org/GEM_NAME is your website, and
+* http://RUBYFORGE_PROJECT.rubyforge.org/GEM_NAME/rdoc is your rdocs
+
 h2. Bonus tasks thanks to Hoe
 
-Your gem uses the Hoe gem to provide a dozen or so useful rake tasks for managing your gem, such as <code>release</code>.
+Your gem uses the Hoe gem to provide a dozen or so useful rake tasks for managing your gem, such as <code>release</code>, <code>check_manifest</code> and <code>publish_docs</code>.
 
 See them all with:
 
 <pre>rake -T</pre>
 
-Remember, the Rakefile is yours to extend as you please with more rake tasks, such as the <code>website</code> tasks already added.
+Remember, the Rakefile is yours to extend as you please with more rake tasks, such as the <code>website</code> tasks which are already added.
 
 For more information about each task, see the "Hoe README":http://seattlerb.rubyforge.org/hoe/
 

data/website/rubyforge.html

@@ -33,7 +33,7 @@
     <h1>New Gem Generator</h1>
     <div id="version" class="clickable" onclick='document.location = "http://rubyforge.org/projects/newgem"; return false'>
       Get Version
-      <a href="http://rubyforge.org/projects/newgem" class="numbers">0.10.1</a>
+      <a href="http://rubyforge.org/projects/newgem" class="numbers">0.10.2</a>
     </div>
     <h1>&#x2192; using &#8216;rubyforge&#8217;</h1>
 

data/website/version-raw.js

@@ -1,3 +1,3 @@
 // Announcement JS file
-var version = "0.10.1";
+var version = "0.10.2";
 MagicAnnouncement.show('compositekeys', version);

data/website/version.js

@@ -1,4 +1,4 @@
 // Version JS file
-var version = "0.10.1";
+var version = "0.10.2";
 
 document.write(" - " + version);

metadata

@@ -3,8 +3,8 @@ rubygems_version: 0.9.4
 specification_version: 1
 name: newgem
 version: !ruby/object:Gem::Version 
-  version: 0.10.1
-date: 2007-05-24 00:00:00 +02:00
+  version: 0.10.2
+date: 2007-05-25 00:00:00 +02:00
 summary: Make your own gems at home
 require_paths: 
 - lib
@@ -75,6 +75,7 @@ files:
 test_files: 
 - test/test_helper.rb
 - test/test_newgem.rb
+- test/test_svn.rb
 rdoc_options: 
 - --main
 - README.txt