for SD
History
-
2011-05-19 22:32:34
Missing author
1148
http://spang.cc/data/sd-bugs/
-
-
2009-08-10 15:26:31
spang@bestpractical.com
1131
7446405e-ebea-11dd-8386-e1c54aff8af6
-
-
created
set to
2009-08-10 15:26:31
-
creator
set to
spang@bestpractical.com
-
original_replica
set to
7446405E-EBEA-11DD-8386-E1C54AFF8AF6
-
content
set to
Database = SD's bugs
Replica = the copy of SD's bugs that are on my laptop
-
ticket
set to
2E0408FC-85C2-11DE-9B4A-18976EA1EC51
-
2009-08-10 15:26:31
spang@bestpractical.com
1130
7446405e-ebea-11dd-8386-e1c54aff8af6
-
-
owner
set to
spang@bestpractical.com
-
creator
set to
spang@bestpractical.com
-
original_replica
set to
7446405E-EBEA-11DD-8386-E1C54AFF8AF6
-
status
set to
new
-
reporter
set to
spang@bestpractical.com
-
created
set to
2009-08-10 15:26:30
-
component
set to
docs
-
summary
set to
database/replica distinction in prophet glossary
-
milestone
set to
diana
-
2009-08-10 14:48:00
spang@bestpractical.com
1129
7446405e-ebea-11dd-8386-e1c54aff8af6
-
-
created
set to
2009-08-10 14:48:00
-
creator
set to
spang@bestpractical.com
-
original_replica
set to
7446405E-EBEA-11DD-8386-E1C54AFF8AF6
-
content
set to
When running commands in-process, don't use set_editor_script,
instead refactor the editor scripts to be methods that are set
by Prophet::Test::set_editor, because the Prophet test suite by
default sets the Prophet edit method to do nothing.
-
ticket
set to
CC7DBF1A-85BC-11DE-AEA3-07866EA1EC51
-
2009-08-10 14:47:59
spang@bestpractical.com
1128
7446405e-ebea-11dd-8386-e1c54aff8af6
-
-
owner
set to
spang@bestpractical.com
-
creator
set to
spang@bestpractical.com
-
original_replica
set to
7446405E-EBEA-11DD-8386-E1C54AFF8AF6
-
status
set to
new
-
reporter
set to
spang@bestpractical.com
-
created
set to
2009-08-10 14:47:59
-
component
set to
tests
-
summary
set to
prophet tests that spawn editor command need refactor
-
milestone
set to
cavil
-
2009-08-07 15:47:14
spang@bestpractical.com
1127
7446405e-ebea-11dd-8386-e1c54aff8af6
-
-
owner
set to
spang@bestpractical.com
-
2009-08-07 15:47:03
spang@bestpractical.com
1126
7446405e-ebea-11dd-8386-e1c54aff8af6
-
-
created
set to
2009-08-07 15:47:03
-
summary
set to
log command barfs when PROPHET_REPO set to invalid repo
-
component
set to
core
-
creator
set to
spang@bestpractical.com
-
original_replica
set to
7446405E-EBEA-11DD-8386-E1C54AFF8AF6
-
status
set to
new
-
milestone
set to
cavil
-
reporter
set to
spang@bestpractical.com
-
2009-08-06 10:27:14
spang@bestpractical.com
1125
7446405e-ebea-11dd-8386-e1c54aff8af6
-
-
status
changed from
new
to
closed
-
2009-08-06 10:24:38
spang@bestpractical.com
1124
7446405e-ebea-11dd-8386-e1c54aff8af6
-
-
status
changed from
new
to
closed
-
2009-07-20 18:12:15
spang@bestpractical.com
1123
7446405e-ebea-11dd-8386-e1c54aff8af6
-
-
component
changed from
core
to
cli
-
2009-08-07 12:57:38
jesse@bestpractical.com
1138
09e374fa-ebd3-11dd-9a7a-bf638f31e82d
-
-
created
set to
2009-08-07 12:57:38
-
creator
set to
jesse@bestpractical.com
-
original_replica
set to
09E374FA-EBD3-11DD-9A7A-BF638F31E82D
-
content
set to
You might want to look at doing this as a hardcoded set of "buttons that perform a set of updates on the current ticket.
eventually, those could go into config. but for starters, hardcoded is fine.
make sure that ticket updates can only happen on post, not get ;)
-
ticket
set to
9BBBBCE4-DEA8-11DD-A16D-3B073D5AF197
-
2009-08-07 12:57:38
jesse@bestpractical.com
1137
09e374fa-ebd3-11dd-9a7a-bf638f31e82d
-
-
owner
changed from
jesse@bestpractical.com
to
spang@bestpractical.com
-
2009-08-07 12:55:46
jesse@bestpractical.com
1136
09e374fa-ebd3-11dd-9a7a-bf638f31e82d
-
-
created
set to
2009-08-07 12:55:46
-
creator
set to
jesse@bestpractical.com
-
original_replica
set to
09E374FA-EBD3-11DD-9A7A-BF638F31E82D
-
content
set to
this may now be done, but wants checking
-
ticket
set to
2F25FA7E-5440-11DD-8147-BE686DC618CE
-
2009-08-07 12:55:34
jesse@bestpractical.com
1135
09e374fa-ebd3-11dd-9a7a-bf638f31e82d
-
-
owner
changed from
sartak@bestpractical.com
to
spang@bestpractical.com
-
2009-08-07 12:55:08
jesse@bestpractical.com
1134
09e374fa-ebd3-11dd-9a7a-bf638f31e82d
-
-
owner
set to
spang@bestpractical.com
-
2009-08-07 12:29:14
jesse@bestpractical.com
1133
09e374fa-ebd3-11dd-9a7a-bf638f31e82d
-
-
created
set to
2009-08-07 12:29:14
-
creator
set to
jesse@bestpractical.com
-
original_replica
set to
09E374FA-EBD3-11DD-9A7A-BF638F31E82D
-
content
set to
actually, it should do two - one that's human readable and one that serialized data for app consumption.
the second one is at least partially implemented
also, the sd server should provide a live version
-
ticket
set to
3A7A9798-57C6-11DD-8775-82266EC618CE
-
2009-08-07 12:29:14
jesse@bestpractical.com
1132
09e374fa-ebd3-11dd-9a7a-bf638f31e82d
-
-
owner
changed from
sartak@bestpractical.com
to
spang@bestpractical.com
-
summary
changed from
publish should create a static rss file
to
publish should create a static Atom feed
-
2009-08-07 12:24:02
jesse@bestpractical.com
1131
09e374fa-ebd3-11dd-9a7a-bf638f31e82d
-
-
created
set to
2009-08-07 12:24:02
-
summary
set to
editable grid view for tickets
-
component
set to
webui
-
creator
set to
jesse@bestpractical.com
-
original_replica
set to
09E374FA-EBD3-11DD-9A7A-BF638F31E82D
-
status
set to
new
-
milestone
set to
diana
-
reporter
set to
jesse@bestpractical.com
-
2009-08-07 12:23:23
jesse@bestpractical.com
1130
09e374fa-ebd3-11dd-9a7a-bf638f31e82d
-
-
created
set to
2009-08-07 12:23:23
-
creator
set to
jesse@bestpractical.com
-
original_replica
set to
09E374FA-EBD3-11DD-9A7A-BF638F31E82D
-
content
set to
then write some tests and get some friendly cryptographers to review it
-
ticket
set to
19C4AF58-834D-11DE-9973-DBDD6A20C32D
-
2009-08-07 12:23:23
jesse@bestpractical.com
1129
09e374fa-ebd3-11dd-9a7a-bf638f31e82d
-
-
created
set to
2009-08-07 12:23:23
-
summary
set to
spec the design for gpg-signed changesets
-
component
set to
core
-
creator
set to
jesse@bestpractical.com
-
original_replica
set to
09E374FA-EBD3-11DD-9A7A-BF638F31E82D
-
status
set to
new
-
milestone
set to
diana
-
reporter
set to
jesse@bestpractical.com