ditz 0.1.1 → 0.1.2

data/Changelog

@@ -1,3 +1,5 @@
+== 0.1.2 / 2008-04-04
+* bugfix: add_reference very broken
 == 0.1.1 / 2008-04-04
 * bugfix: bugfix/feature question always returns feature
 == 0.1 / 2008-04-02

data/Rakefile

@@ -41,7 +41,7 @@ task :upload_webpage_images => (SCREENSHOTS + SCREENSHOTS_SMALL) do |t|
 end
 
 task :upload_report do |t|
-  sh "ditz html ditz"
+  sh "ruby -Ilib bin/ditz html ditz"
   sh "scp -Cr ditz wmorgan@rubyforge.org:/var/www/gforge-projects/ditz/"
 end
 

data/lib/ditz.rb

@@ -1,6 +1,6 @@
 module Ditz
 
-VERSION = "0.1.1"
+VERSION = "0.1.2"
 
 def debug s
   puts "# #{s}" if $opts[:verbose]

data/lib/index.rhtml

@@ -40,7 +40,7 @@
   <p>No past releases.</p>
 <% else %>
   <ul>
-  <% past_releases.each do |r| %>
+  <% past_releases.sort_by { |r| r.release_time }.reverse.each do |r| %>
     <li><%= link_to r, "Release #{r.name}" %>, released <%= r.release_time.pretty_date %>. </li>
   <% end %>
   </ul>

data/lib/operator.rb

@@ -82,7 +82,8 @@ EOS
     issue = project.issue_for issue_name
     reference = ask "Reference"
     comment = ask_multiline "Comments"
-    issue.add_reference reference, config.user, comment
+    issue.add_reference reference
+    issue.log "added reference #{issue.references.size}", config.user, comment
     puts "Added reference to #{issue.name}"
   end
 

metadata

@@ -1,34 +1,33 @@
 --- !ruby/object:Gem::Specification 
+rubygems_version: 0.9.0
+specification_version: 1
 name: ditz
 version: !ruby/object:Gem::Version 
-  version: 0.1.1
+  version: 0.1.2
+date: 2008-04-04 00:00:00 -07:00
+summary: A simple issue tracker designed to integrate well with distributed version control systems like git and darcs. State is saved to a YAML file kept under version control, allowing issues to be closed/added/modified as part of a commit.
+require_paths: 
+- lib
+email: wmorgan-ditz@masanjin.net
+homepage: http://ditz.rubyforge.org
+rubyforge_project: ditz
+description: "Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like darcs and git. Ditz maintains an issue database file on disk, written in a line-based and human-editable format. This file is kept under version control, alongside project code.  Changes in issue state is handled by version control like code change: included as part of a commit, merged with changes from other developers, conflict-resolved in the standard manner, etc.  Ditz provides a simple, console-based interface for creating and updating the issue database file, and some rudimentary HTML generation capabilities for producing world-readable status pages. It offers no central public method of bug submission.  Synopsis:  # set up project. creates the bugs.yaml file. 1. ditz init 2. ditz add-release  # add an issue 3. ditz add  # where am i? 4. ditz status 5. ditz todo  # do work 6. write code 7. ditz close <issue-id> 8. commit 9. goto 3  # finished! 10. ditz release <release-name>"
+autorequire: 
+default_executable: 
+bindir: bin
+has_rdoc: true
+required_ruby_version: !ruby/object:Gem::Version::Requirement 
+  requirements: 
+  - - ">"
+    - !ruby/object:Gem::Version 
+      version: 0.0.0
+  version: 
 platform: ruby
+signing_key: 
+cert_chain: 
+post_install_message: 
 authors: 
 - William Morgan
-autorequire: 
-bindir: bin
-cert_chain: []
-
-date: 2008-04-04 00:00:00 -07:00
-default_executable: 
-dependencies: 
-- !ruby/object:Gem::Dependency 
-  name: trollop
-  version_requirement: 
-  version_requirements: !ruby/object:Gem::Requirement 
-    requirements: 
-    - - ">="
-      - !ruby/object:Gem::Version 
-        version: "1.7"
-    version: 
-description: "Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like darcs and git. Ditz maintains an issue database file on disk, written in a line-based and human-editable format. This file is kept under version control, alongside project code.  Changes in issue state is handled by version control like code change: included as part of a commit, merged with changes from other developers, conflict-resolved in the standard manner, etc.  Ditz provides a simple, console-based interface for creating and updating the issue database file, and some rudimentary HTML generation capabilities for producing world-readable status pages. It offers no central public method of bug submission.  Synopsis:  # set up project. creates the bugs.yaml file. 1. ditz init 2. ditz add-release  # add an issue 3. ditz add  # where am i? 4. ditz status 5. ditz todo  # do work 6. write code 7. ditz close <issue-id> 8. commit 9. goto 3  # finished! 10. ditz release <release-name>"
-email: wmorgan-ditz@masanjin.net
-executables: 
-- ditz
-extensions: []
-
-extra_rdoc_files: 
-- README.txt
 files: 
 - Changelog
 - README.txt
@@ -48,32 +47,26 @@ files:
 - lib/style.css
 - lib/unassigned.rhtml
 - lib/util.rb
-has_rdoc: true
-homepage: http://ditz.rubyforge.org
-post_install_message: 
+test_files: []
+
 rdoc_options: 
 - --main
 - README.txt
-require_paths: 
-- lib
-required_ruby_version: !ruby/object:Gem::Requirement 
-  requirements: 
-  - - ">="
-    - !ruby/object:Gem::Version 
-      version: "0"
-  version: 
-required_rubygems_version: !ruby/object:Gem::Requirement 
-  requirements: 
-  - - ">="
-    - !ruby/object:Gem::Version 
-      version: "0"
-  version: 
-requirements: []
+extra_rdoc_files: 
+- README.txt
+executables: 
+- ditz
+extensions: []
 
-rubyforge_project: ditz
-rubygems_version: 1.0.1
-signing_key: 
-specification_version: 2
-summary: A simple issue tracker designed to integrate well with distributed version control systems like git and darcs. State is saved to a YAML file kept under version control, allowing issues to be closed/added/modified as part of a commit.
-test_files: []
+requirements: []
 
+dependencies: 
+- !ruby/object:Gem::Dependency 
+  name: trollop
+  version_requirement: 
+  version_requirements: !ruby/object:Gem::Version::Requirement 
+    requirements: 
+    - - ">="
+      - !ruby/object:Gem::Version 
+        version: "1.7"
+    version: