ditz 0.2 → 0.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -19,6 +19,14 @@ module Enumerable
19
19
  each { |e| x = yield(e); return x if x }
20
20
  nil
21
21
  end
22
+
23
+ def group_by
24
+ inject({}) do |groups, element|
25
+ (groups[yield(element)] ||= []) << element
26
+ groups
27
+ end
28
+ end if RUBY_VERSION < '1.9'
29
+
22
30
  end
23
31
 
24
32
  class Array
metadata CHANGED
@@ -1,33 +1,35 @@
1
1
  --- !ruby/object:Gem::Specification
2
- rubygems_version: 0.9.0
3
- specification_version: 1
4
2
  name: ditz
5
3
  version: !ruby/object:Gem::Version
6
- version: "0.2"
7
- date: 2008-04-11 07:00:00 Z
8
- 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.
9
- require_paths:
10
- - lib
11
- email: wmorgan-ditz@masanjin.net
12
- homepage: http://ditz.rubyforge.org
13
- rubyforge_project: ditz
14
- 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>"
15
- autorequire:
16
- default_executable:
17
- bindir: bin
18
- has_rdoc: true
19
- required_ruby_version: !ruby/object:Gem::Version::Requirement
20
- requirements:
21
- - - ">"
22
- - !ruby/object:Gem::Version
23
- version: 0.0.0
24
- version:
4
+ version: "0.3"
25
5
  platform: ruby
26
- signing_key:
27
- cert_chain:
28
- post_install_message:
29
6
  authors:
30
7
  - William Morgan
8
+ autorequire:
9
+ bindir: bin
10
+ cert_chain: []
11
+
12
+ date: 2008-06-04 07:00:00 Z
13
+ default_executable:
14
+ dependencies:
15
+ - !ruby/object:Gem::Dependency
16
+ name: trollop
17
+ version_requirement:
18
+ version_requirements: !ruby/object:Gem::Requirement
19
+ requirements:
20
+ - - ">="
21
+ - !ruby/object:Gem::Version
22
+ version: "1.7"
23
+ version:
24
+ 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 directory on disk, with files written in a line-based and human-editable format. This directory 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 files, 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>"
25
+ email: wmorgan-ditz@masanjin.net
26
+ executables:
27
+ - ditz
28
+ - ditz-convert-from-monolith
29
+ extensions: []
30
+
31
+ extra_rdoc_files:
32
+ - README.txt
31
33
  files:
32
34
  - Changelog
33
35
  - README.txt
@@ -49,27 +51,33 @@ files:
49
51
  - lib/style.css
50
52
  - lib/unassigned.rhtml
51
53
  - lib/util.rb
52
- test_files: []
53
-
54
+ - lib/hook.rb
55
+ has_rdoc: true
56
+ homepage: http://ditz.rubyforge.org
57
+ post_install_message:
54
58
  rdoc_options:
55
59
  - --main
56
60
  - README.txt
57
- extra_rdoc_files:
58
- - README.txt
59
- executables:
60
- - ditz
61
- - ditz-convert-from-monolith
62
- extensions: []
63
-
61
+ require_paths:
62
+ - lib
63
+ required_ruby_version: !ruby/object:Gem::Requirement
64
+ requirements:
65
+ - - ">="
66
+ - !ruby/object:Gem::Version
67
+ version: "0"
68
+ version:
69
+ required_rubygems_version: !ruby/object:Gem::Requirement
70
+ requirements:
71
+ - - ">="
72
+ - !ruby/object:Gem::Version
73
+ version: "0"
74
+ version:
64
75
  requirements: []
65
76
 
66
- dependencies:
67
- - !ruby/object:Gem::Dependency
68
- name: trollop
69
- version_requirement:
70
- version_requirements: !ruby/object:Gem::Version::Requirement
71
- requirements:
72
- - - ">="
73
- - !ruby/object:Gem::Version
74
- version: "1.7"
75
- version:
77
+ rubyforge_project: ditz
78
+ rubygems_version: 1.1.1
79
+ signing_key:
80
+ specification_version: 2
81
+ 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.
82
+ test_files: []
83
+