ohac-ditz 0.5.1 → 0.5.2

Sign up to get free protection for your applications and to get access to all the features.
Files changed (14) hide show
  1. data/Changelog +1 -1
  2. data/Manifest.txt +0 -1
  3. data/Rakefile +3 -3
  4. data/ReleaseNotes +5 -0
  5. data/bin/coditz.rb +276 -0
  6. data/contrib/bookmarklet.js +1 -0
  7. data/lib/ditz.rb +1 -1
  8. data/lib/ditz/plugins/icalendar.rb +64 -0
  9. data/lib/ditz/plugins/issue-timetracker.rb +52 -0
  10. data/lib/ditz/plugins/mercurial.rb +48 -0
  11. data/lib/ditz/plugins/sha-names.rb +35 -0
  12. data/man/man1/ditz.1 +1 -1
  13. data/sheila/sheila.rb +876 -0
  14. metadata +43 -7
metadata CHANGED
@@ -1,16 +1,16 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: ohac-ditz
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.5.1
4
+ version: 0.5.2
5
5
  platform: ruby
6
6
  authors:
7
- - William Morgan
7
+ - OHASHI Hideya
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
11
 
12
- date: 2008-09-05 00:00:00 +09:00
13
- default_executable: ditz
12
+ date: 2010-01-15 15:00:00 Z
13
+ default_executable:
14
14
  dependencies:
15
15
  - !ruby/object:Gem::Dependency
16
16
  name: trollop
@@ -32,10 +32,39 @@ dependencies:
32
32
  - !ruby/object:Gem::Version
33
33
  version: "0.3"
34
34
  version:
35
- description: "Ditz is a simple, light-weight distributed issue tracker designed to work with distributed version control systems like git, darcs, Mercurial, and Bazaar. It can also be used with centralized systems like SVN. Ditz maintains an issue database directory on disk, with files written in a line-based and human-editable format. This directory can be kept under version control, alongside project code. Ditz provides a simple, console-based interface for creating and updating the issue database files, and some basic static HTML generation capabilities for producing world-readable status pages (for a demo, see the ditz ditz page). Ditz includes a robust plugin system for adding commands, model fields, and modifying output. See PLUGINS.txt for documentation on the pre-shipped plugins. Ditz currently offers no central public method of bug submission. == USING DITZ There are several different ways to use Ditz: 1. Treat issue change the same as code change: include it as part of commits, and merge it with changes from other developers, resolving conflicts in the usual manner. 2. Keep the issue database in the repository but in a separate branch. Issue changes can be managed by your VCS, but is not tied directly to code commits. 3. Keep the issue database separate and not under VCS at all."
36
- email: wmorgan-ditz@masanjin.net
35
+ description: |-
36
+ Ditz is a simple, light-weight distributed issue tracker designed to work with
37
+ distributed version control systems like git, darcs, Mercurial, and Bazaar. It
38
+ can also be used with centralized systems like SVN.
39
+
40
+ Ditz maintains an issue database directory on disk, with files written in a
41
+ line-based and human-editable format. This directory can be kept under version
42
+ control, alongside project code.
43
+
44
+ Ditz provides a simple, console-based interface for creating and updating the
45
+ issue database files, and some basic static HTML generation capabilities for
46
+ producing world-readable status pages (for a demo, see the ditz ditz page).
47
+
48
+ Ditz includes a robust plugin system for adding commands, model fields, and
49
+ modifying output. See PLUGINS.txt for documentation on the pre-shipped plugins.
50
+
51
+ Ditz currently offers no central public method of bug submission.
52
+
53
+ == USING DITZ
54
+
55
+ There are several different ways to use Ditz:
56
+
57
+ 1. Treat issue change the same as code change: include it as part of commits,
58
+ and merge it with changes from other developers, resolving conflicts in the
59
+ usual manner.
60
+ 2. Keep the issue database in the repository but in a separate branch. Issue
61
+ changes can be managed by your VCS, but is not tied directly to code
62
+ commits.
63
+ 3. Keep the issue database separate and not under VCS at all.
64
+ email: ohachige@gmail.com
37
65
  executables:
38
66
  - ditz
67
+ - coditz.rb
39
68
  extensions: []
40
69
 
41
70
  extra_rdoc_files:
@@ -66,6 +95,7 @@ files:
66
95
  - lib/ditz/plugins/git.rb
67
96
  - lib/ditz/plugins/issue-claiming.rb
68
97
  - lib/ditz/plugins/issue-labeling.rb
98
+ - lib/ditz/plugins/issue-timetracker.rb
69
99
  - lib/ditz/util.rb
70
100
  - lib/ditz/view.rb
71
101
  - lib/ditz/views.rb
@@ -83,6 +113,12 @@ files:
83
113
  - share/ditz/yellow-bar.png
84
114
  - man/man1/ditz.1
85
115
  - setup.rb
116
+ - bin/coditz.rb
117
+ - contrib/bookmarklet.js
118
+ - lib/ditz/plugins/icalendar.rb
119
+ - lib/ditz/plugins/mercurial.rb
120
+ - lib/ditz/plugins/sha-names.rb
121
+ - sheila/sheila.rb
86
122
  has_rdoc: true
87
123
  homepage: http://ditz.rubyforge.org
88
124
  licenses: []
@@ -110,7 +146,7 @@ requirements: []
110
146
  rubyforge_project: ditz
111
147
  rubygems_version: 1.3.5
112
148
  signing_key:
113
- specification_version: 2
149
+ specification_version: 3
114
150
  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.
115
151
  test_files: []
116
152