History

template tests should compare lines not entire template (245)

• owner set to spang@bestpractical.com
• creator set to spang
• original_replica set to 9A3BFB90-B748-11DD-B155-797E8947A455
• status set to new
• reporter set to spang@bestpractical.com
• created set to 2009-01-16 12:26:06
• component set to core
• summary set to template tests should compare lines not entire template
• milestone set to cavil

sd should handle multiple dbs (237)

• owner set to spang@bestpractical.com

sd help init should redirect to sd help intro (231)

• status changed from new to closed

sd ticket create needs a verbose mode (178)

• status changed from open to closed

• content changed from [{"due":"when this ticket must be finished by (ISO 8601 format)","owner":"the email address of the person who is responsible for this ticket","reporter":"the email address of the person who reported this ticket","summary":"a one-line summary of what the ticket is about"}] to [{"due":"when this ticket must be finished by (ISO 8601 format)","owner":"the email address of the person who is responsible for this ticket","reporter":"the email address of the person who reported this ticket","summary":"a one-line summary of what this ticket is about"}]

Comment on: common_ticket_props should be overrideable by a config file setting (243)

• created set to 2009-01-14 20:27:53
• creator set to spang
• original_replica set to 9A3BFB90-B748-11DD-B155-797E8947A455
• content set to 13:07 < obra> christine: I'm not sure about making default_props_to_show a project-wide db setting rather than a config file setting. can you tell me about your rationale? 15:15 < christine> hmm. I hadn't actually considered config file setting vs db setting. I was just thinking it shouldn't be hard-coded/not changeable. 15:17 < christine> on the one hand it makes sense to be a db setting if e.g. a project uses a non-standard prop heavily, but on the other hand users might want to change it, I guess. 15:22 < obra> perhaps "db setting overridable by config file setting"?
• ticket set to D1EABE80-E279-11DD-BC55-CEB220C5F1DA

common_ticket_props should be overrideable by a config file setting (243)

• owner set to spang@bestpractical.com
• creator set to spang
• original_replica set to 9A3BFB90-B748-11DD-B155-797E8947A455
• status set to new
• reporter set to spang@bestpractical.com
• created set to 2009-01-14 20:27:53
• component set to core
• summary set to default_props_to_show should be overrideable by a config file setting
• milestone set to cavil

Comment on: sd should handle multiple dbs (237)

• created set to 2009-01-14 12:15:46
• creator set to spang
• original_replica set to 9A3BFB90-B748-11DD-B155-797E8947A455
• content set to 13:11 < mst> the problem with ~/.sd_current_replica 13:11 < mst> is that then that'll affect every shell 13:11 < mst> which is basically shit 13:12 < mst> probably the correct approach here is to have a file name in an env var 13:12 < mst> then people who want it global to that user+host set SD_REPO_FILE=~/.sd_current_replica 13:13 < mst> andx people who want it local to a shell set it to ~/.sd_current_replica_${pid} or whatever
• ticket set to 6370BCA6-E1BC-11DD-BC61-FADF20C5F1DA

Comment on: sd should handle multiple dbs (237)

• created set to 2009-01-14 12:08:05
• creator set to spang
• original_replica set to 9A3BFB90-B748-11DD-B155-797E8947A455
• content set to For switching within sd shell: 10:09 < obra> so, what determines what replica you're working with is SD_REPO 10:10 < obra> other stuff gets pulled from that at startup 10:11 < obra> i worry about cleaning out everything at runtime 10:11 < obra> the cleanest way to do it is to set SD_REPO and then reexec sd 10:02 < obra> we could make it transparent if we could keep history for the shell across runs 10:02 < obra> which i think is a bug, not "unwritten"
• ticket set to 6370BCA6-E1BC-11DD-BC61-FADF20C5F1DA

sd ticket create needs a verbose mode (178)

• status changed from new to open

Comment on: sd ticket create needs a verbose mode (178)

• created set to 2009-01-14 12:05:23
• creator set to spang
• original_replica set to 9A3BFB90-B748-11DD-B155-797E8947A455
• content set to This is done except for tests.
• ticket set to 316F9DEC-8E2B-11DD-893A-91A575A662F7

• content set to [{"due":"when this ticket must be finished by (ISO 8601 format)","owner":"the email address of the person who is responsible for this ticket","reporter":"the email address of the person who reported this ticket","summary":"a one-line summary of what the ticket is about"}]
• label set to prop_descriptions

Comment on: sd should handle multiple dbs (237)

• created set to 2009-01-13 21:51:53
• creator set to spang
• original_replica set to 9A3BFB90-B748-11DD-B155-797E8947A455
• content set to 10:38 < obra> I'd think about something like ~/.sd_current_replica as a symlink 13:11 < mst> the problem with ~/.sd_current_replica 13:11 < mst> is that then that'll affect every shell 13:11 < mst> which is basically shit 13:12 < mst> probably the correct approach here is to have a file name in an env var 13:12 < mst> then people who want it global to that user+host set SD_REPO_FILE=~/.sd_current_replica 13:13 < mst> andx people who want it local to a shell set it to ~/.sd_current_replica_${pid} or whatever
• ticket set to 6370BCA6-E1BC-11DD-BC61-FADF20C5F1DA

sd should handle multiple dbs (237)

• created set to 2009-01-13 21:51:52
• summary set to sd should handle multiple dbs
• component set to core
• creator set to spang
• original_replica set to 9A3BFB90-B748-11DD-B155-797E8947A455
• status set to new
• milestone set to diana
• reporter set to spang@bestpractical.com

flow for templates with errors is bad (232)

• status changed from new to open

Comment on: flow for templates with errors is bad (232)

• created set to 2009-01-13 17:37:57
• creator set to spang
• original_replica set to 9A3BFB90-B748-11DD-B155-797E8947A455
• content set to Also, "your template contained errors" is not that great an error message. We should be able to sub the record type in there, shouldn't we? Users don't know that this involves a template at all and shouldn't have to.
• ticket set to 5B36E1E8-E197-11DD-B863-D0BA20C5F1DA

Comment on: prophet needs a glossary (234)

• created set to 2009-01-13 17:29:52
• creator set to spang
• original_replica set to 9A3BFB90-B748-11DD-B155-797E8947A455
• content set to Terms like 'config' (which refers to local configuration) and 'settings' (which refers to db-specific settings which are db items because they need to propagate with the db) are difficult to understand for newcomers, we should have a doc that explains them.
• ticket set to C8FA6C90-E197-11DD-BE73-59BB20C5F1DA

prophet needs a glossary (234)

• owner set to spang@bestpractical.com
• creator set to spang
• original_replica set to 9A3BFB90-B748-11DD-B155-797E8947A455
• status set to new
• reporter set to spang@bestpractical.com
• created set to 2009-01-13 17:29:51
• component set to core
• summary set to prophet needs a glossary
• milestone set to cavil

Comment on: flow for templates with errors is bad (232)

• created set to 2009-01-13 17:26:47
• creator set to spang
• original_replica set to 9A3BFB90-B748-11DD-B155-797E8947A455
• content set to Asks you if you want to keep go back to editing without telling you something went wrong, etc. (if a validation fails)
• ticket set to 5B36E1E8-E197-11DD-B863-D0BA20C5F1DA