ditz 0.1 → 0.1.1

data/Changelog

@@ -1,2 +1,4 @@
+== 0.1.1 / 2008-04-04
+* bugfix: bugfix/feature question always returns feature
 == 0.1 / 2008-04-02
 * Initial release!

data/README.txt

@@ -9,9 +9,9 @@ http://ditz.rubyforge.org
 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 can be kept under version control alongside project code, and issue state
-change can then be handled like code changes: modified as part of a commit,
-merged with other state changes from other developers, conflict-resolved in the
+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

data/Rakefile

@@ -13,7 +13,7 @@ Hoe.new('ditz', Ditz::VERSION) do |p|
   p.author = "William Morgan"
   p.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."
 
-  p.description = p.paragraphs_of('README.txt', 4..5, 9..18).join("\n\n").gsub(/== SYNOPSIS/, "Synopsis")
+  p.description = p.paragraphs_of('README.txt', 4..11).join("\n\n").gsub(/== SYNOPSIS/, "Synopsis:")
   p.url = "http://ditz.rubyforge.org"
   p.changes = p.paragraphs_of('Changelog', 0..0).join("\n\n")
   p.email = "wmorgan-ditz@masanjin.net"

data/lib/ditz.rb

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

data/lib/model-objects.rb

@@ -209,7 +209,7 @@ class Issue < ModelObject
   end
 
   def get_type config, project
-    ask "Is this a (b)ugfix or a (f)eature?", :restrict => /^[bf]$/
+    type = ask "Is this a (b)ugfix or a (f)eature?", :restrict => /^[bf]$/
     type == "b" ? :bugfix : :feature
   end
 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification 
 name: ditz
 version: !ruby/object:Gem::Version 
-  version: "0.1"
+  version: 0.1.1
 platform: ruby
 authors: 
 - William Morgan
@@ -9,7 +9,7 @@ autorequire:
 bindir: bin
 cert_chain: []
 
-date: 2008-04-02 00:00:00 -07:00
+date: 2008-04-04 00:00:00 -07:00
 default_executable: 
 dependencies: 
 - !ruby/object:Gem::Dependency 
@@ -21,7 +21,7 @@ dependencies:
       - !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 can be kept under version control alongside project code, and issue state change can then be handled like code changes: modified as part of a commit, merged with other state 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.  # 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>  == THE DITZ DATA MODEL  Ditz includes the bare minimum set of features necessary for open-source development. Features like time spent, priority, assignment of tasks to developers, due dates, etc. are purposely excluded.  A ditz project consists of issues, releases and components.  Issues: Issues are the fundamental currency of issue tracking. A ditz issue is either a feature or a bug, but this distinction doesn't affect anything other than how they're displayed.  Each issue belongs to exactly one component, and is part of zero or one releases.  Each issues has an exportable id, in the form of 40 random hex characters. This id is \"guaranteed\" to be unique across all possible issues and developers, present and future. Issue ids are typically not exposed to the user.  Issues also have a non-exportable name, which is short and human-readable. All ditz commands use issue names instead of issue ids. Issue ids may change in certain circumstances, specifically after a \"ditz drop\" command."
+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