meta_project 0.4.14 → 0.4.15

data/CHANGES

@@ -1,5 +1,11 @@
 = MetaProject Changelog
 
+== Version 0.4.15
+
+Bugfix release
+
+* Nothing really new from 0.14 except that this time the code is committed to CVS (forgot that last time)
+
 == Version 0.4.14
 
 Bugfix release

data/README

@@ -1,28 +1,18 @@
-= MetaProject 0.4.14
+= MetaProject 0.4.15
 
-MetaProject (formerly XForge) is a library that allows interaction with various project hosting servers, issue trackers, SCMs and SCM browsers through a common API.
+MetaProject is a library that allows interaction with various project hosting servers, issue trackers, SCMs and SCM browsers through a common API.
 
 MetaProject also includes is a Quick Release System (QRS) for [RubyForge, SourceForge and other SourceForge clones] (commonly referred to as XForge throughout the documentation) as well as RAA and Freshmeat. QRS support for other hosts is in the pipe.
 
 == Feature overview
 
-=== RSCM related
-
-* Obtain preconfigured RSCM:http://rscm.rubyforge.org objects.
-
-=== SCM browser related
-
-* Obtain preconfigured SCM browser proxy objects that can generate various links with a simple API.
-
-* Treat files in the SCM browser just as stdlib Pathname object (only a subset is provided)
-
-=== QRS related
+=== QRS (Quick Release System) related
 
 * QRS: Create/Upload new releases (with multiple files if desired).
 
 * Rake integration (use the QRS from Rake scripts).
 
-* Publish XForge news items for a project.
+* Publish news items for XForge project.
 
 * Publish on RAA (SOAP under the hood)
 
@@ -44,6 +34,16 @@ MetaProject also includes is a Quick Release System (QRS) for [RubyForge, Source
 
 * Query home page URLs for a project.
 
+=== RSCM related
+
+* Obtain preconfigured RSCM:http://rscm.rubyforge.org objects.
+
+=== SCM browser related
+
+* Obtain preconfigured SCM browser proxy objects that can generate various links with a simple API.
+
+* Treat files in the SCM browser just as stdlib Pathname object (only a subset of the Pathname API is provided)
+
 == Screen Scraping
 
 MetaProject uses <a href="http://www.catb.org/~esr/jargon/html/S/screen-scraping.html">screen scraping</a> heavily. This is a last-resort technique which is only used when there is no other approach (XML-RPC/SOAP/REST) to retrieve data more reliably. As a result, some of the functionality might break if the HTML of the hosts MetaProject scrapes data from changes. If you think MetaProject is misbehaving because of changed HTML on some external system that MetaProject interacts with, please file a bug report in MetaProject's bug tracker on RubyForge.
@@ -78,8 +78,7 @@ If you're writing an application that interacts with MetaProject, please refer t
 
 === I don't have a CHANGES file that MetaProject's Rake tasks understands. How do I disable it?
 When using the Rake tasks Rake::XForge::Release and Rake::XForge::NewsPublisher, you can omit parsing
-of the CHANGES file by telling the task to omit it. In this case, you also have to specify +release_notes+
-and +release_changes+ to the task. Example:
+of the CHANGES file by specifying +release_notes+ and +release_changes+ to the task. Example:
 
   task :release_files => [:gem] do
     release_files = FileList[

data/Rakefile

@@ -24,7 +24,7 @@ require 'rake/rdoctask'
 #
 # REMEMBER TO KEEP PKG_VERSION IN SYNC WITH THE CHANGES FILE!
 PKG_NAME = "meta_project"
-PKG_VERSION = "0.4.14"
+PKG_VERSION = "0.4.15"
 PKG_FILE_NAME = "#{PKG_NAME}-#{PKG_VERSION}"
 PKG_FILES = FileList[
   '[A-Z]*',

metadata

@@ -3,8 +3,8 @@ rubygems_version: 0.8.11
 specification_version: 1
 name: meta_project
 version: !ruby/object:Gem::Version 
-  version: 0.4.14
-date: 2006-02-27 00:00:00 -06:00
+  version: 0.4.15
+date: 2006-05-03 00:00:00 -05:00
 summary: Ruby library for interacting with project hosting servers, scms and issue trackers.
 require_paths: 
 - lib