for SD

History

Earlier Later

2009-08-20 22:59:44 spang@bestpractical.com 1335 7446405e-ebea-11dd-8386-e1c54aff8af6

write release announcement (474)

due set to 2009-08-21 22:59:44
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-20 22:59:44
component set to core
summary set to write release announcement
milestone set to cavil

2009-08-20 22:55:14 spang@bestpractical.com 1334 7446405e-ebea-11dd-8386-e1c54aff8af6

Comment on: update website "Download" section (472)

created set to 2009-08-20 22:55:14
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to Still recommend using Git, but point toward releases on CPAN.
ticket set to 85b44cb7-8ddc-11de-833e-d18b3ac02388

2009-08-20 22:55:14 spang@bestpractical.com 1333 7446405e-ebea-11dd-8386-e1c54aff8af6

update website "Download" section (472)

owner set to spang@bestpractical.com
due set to 2009-08-21 22:55:14
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-20 22:55:14
summary set to update website "Download" section
component set to docs
milestone set to cavil

2009-08-20 22:53:21 spang@bestpractical.com 1332 7446405e-ebea-11dd-8386-e1c54aff8af6

Comment on: update "SD for SD" website section w/info on submitting bug reports (470)

created set to 2009-08-20 22:53:21
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to Dump them into cpan's RT and we'll sync from there, or GitHub (recommend RT but accept both)
ticket set to 424fec46-8ddc-11de-833e-ad0b44c0f207

2009-08-20 22:53:21 spang@bestpractical.com 1331 7446405e-ebea-11dd-8386-e1c54aff8af6

update "SD for SD" website section w/info on submitting bug reports (470)

owner set to spang@bestpractical.com
due set to 2009-08-21 22:53:21
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-20 22:53:21
summary set to update "SD for SD" website section w/info on submitting bug reports
component set to docs
milestone set to cavil

2009-08-20 22:49:48 spang@bestpractical.com 1330 7446405e-ebea-11dd-8386-e1c54aff8af6

write tutorial document (469)

owner set to spang@bestpractical.com

2009-08-20 22:47:06 spang@bestpractical.com 1329 7446405e-ebea-11dd-8386-e1c54aff8af6

write tutorial document (469)

due set to 2009-08-21 22:47:06
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-20 22:47:06
component set to docs
summary set to write tutorial document
milestone set to cavil

2009-08-20 22:45:36 spang@bestpractical.com 1328 7446405e-ebea-11dd-8386-e1c54aff8af6

Update website with 'contributing' page (467)

component changed from core to docs

2009-08-20 22:44:30 spang@bestpractical.com 1327 7446405e-ebea-11dd-8386-e1c54aff8af6

make sure that local/remote uuid in the different-db merge are not swapped (77)

due set to 2009-08-21 22:44:30

2009-08-20 22:44:17 spang@bestpractical.com 1326 7446405e-ebea-11dd-8386-e1c54aff8af6

sd server readonly mode appears to have vanished (308)

due set to 2009-08-21 22:44:17

2009-08-20 22:44:02 spang@bestpractical.com 1325 7446405e-ebea-11dd-8386-e1c54aff8af6

sd should explode more when it can't figure out user email (414)

due set to 2009-08-21 22:44:02

2009-08-20 22:42:42 spang@bestpractical.com 1324 7446405e-ebea-11dd-8386-e1c54aff8af6

Comment on: Update website with 'contributing' page (467)

created set to 2009-08-20 22:42:42
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to - fix bugs, write tests (link to my coverage dumps), write foreign syncs, come talk to us on #prophet or the mailing list
ticket set to c53bc00a-8dda-11de-833e-80a8fe726beb

2009-08-20 22:42:42 spang@bestpractical.com 1323 7446405e-ebea-11dd-8386-e1c54aff8af6

Update website with 'contributing' page (467)

owner set to spang@bestpractical.com
due set to 2009-08-21 22:42:42
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-20 22:42:42
summary set to Update website with 'contributing' page
component set to core
milestone set to cavil

2009-08-20 22:09:23 spang@bestpractical.com 1322 7446405e-ebea-11dd-8386-e1c54aff8af6

need git commit post-commit hook to close tickets (465)

status changed from new to closed

2009-08-20 22:09:21 spang@bestpractical.com 1321 7446405e-ebea-11dd-8386-e1c54aff8af6

Comment on: need git commit post-commit hook to close tickets (465)

created set to 2009-08-20 22:09:21
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to Closed by git commit 4f04016383d1d36a54757bf2be5dbfa2807f2234
ticket set to 1b64e082-8dcd-11de-8211-a5bbe4e640b7

2009-08-20 21:04:53 spang@bestpractical.com 1320 7446405e-ebea-11dd-8386-e1c54aff8af6

need git commit post-commit hook to close tickets (465)

created set to 2009-08-20 21:04:53
summary set to need git commit post-commit hook to close tickets
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 diana
reporter set to spang@bestpractical.com

2009-08-20 20:16:34 spang@bestpractical.com 1319 7446405e-ebea-11dd-8386-e1c54aff8af6

Comment on: improve sdticket.vim keyword highlighting (463)

created set to 2009-08-20 20:16:34
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to Right now it hightlights keywords even if they're in the wrong line (for example, 'core' in the summary line--or in a comment, even. If we use regexes instead of just simple keyword matches, we can make this better.
ticket set to 5b999afb-8dc6-11de-8001-8a09e62ce327

2009-08-20 20:16:34 spang@bestpractical.com 1318 7446405e-ebea-11dd-8386-e1c54aff8af6

improve sdticket.vim keyword highlighting (463)

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-20 20:16:34
component set to core
summary set to improve sdticket.vim keyword highlighting
milestone set to diana

2009-08-20 19:48:55 spang@bestpractical.com 1317 7446405e-ebea-11dd-8386-e1c54aff8af6

Comment on: sd should explode more when it can't figure out user email (414)

created set to 2009-08-20 19:48:55
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to Done, but needs tests.
ticket set to 0e661c3e-8817-11de-82eb-f5bd9d918618

2009-08-20 19:45:28 spang@bestpractical.com 1316 7446405e-ebea-11dd-8386-e1c54aff8af6

Comment on: log command barfs when PROPHET_REPO set to invalid repo (409)

created set to 2009-08-20 19:45:28
creator set to spang@bestpractical.com
original_replica set to 7446405E-EBEA-11DD-8386-E1C54AFF8AF6
content set to Gives a fine message now that the dispatcher checks for a valid repo for commands that need it
ticket set to 8D62E896-8369-11DE-B655-EF4A1931862D

Earlier Later