History

bad messages on pull from bad url (577)

• owner set to christine@debian.org
• creator set to christine@debian.org
• original_replica set to faa714e0-9953-11de-81f6-91eefc3666f8
• status set to new
• reporter set to christine@debian.org
• created set to 2010-06-20 17:17:40
• component set to cli
• summary set to bad messages on pull from bad url
• milestone set to diana

()

()

• created set to 2009-09-28 04:59:18
• summary set to RT sync shouldn't silently die on wrong password
• component set to rt-sync
• creator set to spang@bestpractical.com
• original_replica set to faa714e0-9953-11de-81f6-91eefc3666f8
• status set to new
• milestone set to diana
• reporter set to spang@bestpractical.com

http://syncwith.us/sd/using is missing an env variable setting step (575)

• created set to 2009-09-11 23:12:27
• summary set to http://syncwith.us/sd/using is missing an env variable setting step
• 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

t/malformed-url.t in Prophet shouldn't try to connect to the web (426)

• component changed from core to tests

Comment on: alias cli bug (502)

• created set to 2009-09-03 04:18:09
• creator set to spang@bestpractical.com
• original_replica set to e26467b0-95c6-11de-80cb-cdb2d2e3ae72
• content set to This is related to props preprocessing in CLIContext.pm
• ticket set to a80e655a-9249-11de-8368-e0f510055f06

I want to be able to say 'bug' instead of 'ticket' (455)

• status changed from new to closed

switch back to UUID::Tiny (after UUID::Tiny 1.02) (437)

• status changed from new to closed

Comment on: switch back to UUID::Tiny (after UUID::Tiny 1.02) (437)

• created set to 2009-09-03 02:42:46
• creator set to spang@bestpractical.com
• original_replica set to e26467b0-95c6-11de-80cb-cdb2d2e3ae72
• content set to Closed by git commit a774328e278e08ad7086a5f445eefc51a0fde792
• ticket set to 67ba10dd-8b9c-11de-815a-c1408031c2cb

Comment on: need Prophet overview doc (561)

• created set to 2009-08-31 01:44:07
• creator set to spang@bestpractical.com
• original_replica set to e26467b0-95c6-11de-80cb-cdb2d2e3ae72
• content set to (1) from 15:29 < allan> christine: I wanted (one or all of): 1) conceptual overview of Prophet (i.e. why should I trust that this stuff works ;) ), 2) API description for Prophet, 3) some docs on ‘sd’ (usage/tutorial/features/etc.)
• ticket set to c4ff9266-95cc-11de-82b2-ed433c2b7f00

Comment on: need "Documentation" section on website (570)

• created set to 2009-08-31 01:43:19
• creator set to spang@bestpractical.com
• original_replica set to e26467b0-95c6-11de-80cb-cdb2d2e3ae72
• content set to 15:47 < allan> I would also suggest some sort of placeholder for doc status which things point to — I know docs are often sparse in the beginning, making a note of that goes a long way 15:47 < allan> especially with such fragmented web presence as prophet 15:48 < christine> allan: good point. you're thinking, say, a 'ducmentation' section on syncwith.us ? 15:48 < allan> fragmented as in: bestpractical.com, syncwith.us, github, CPAN, and that slide thing linked to 15:48 < allan> yes 15:49 * christine nods
• ticket set to a9061f3b-95cf-11de-81a0-bce9d0450afd

need "Documentation" section on website (570)

• owner set to spang@bestpractical.com
• creator set to spang@bestpractical.com
• original_replica set to e26467b0-95c6-11de-80cb-cdb2d2e3ae72
• status set to new
• reporter set to spang@bestpractical.com
• created set to 2009-08-31 01:43:19
• component set to docs
• summary set to need "Documentation" section on website
• milestone set to diana

Comment on: write tutorial document (469)

• created set to 2009-08-31 01:39:57
• creator set to spang@bestpractical.com
• original_replica set to e26467b0-95c6-11de-80cb-cdb2d2e3ae72
• content set to (3) from 15:29 < allan> christine: I wanted (one or all of): 1) conceptual overview of Prophet (i.e. why should I trust that this stuff works ;) ), 2) API description for Prophet, 3) some docs on ‘sd’ (usage/tutorial/features/etc.)
• ticket set to 62ac99f5-8ddb-11de-833e-9f4793675960

Comment on: protect users from accidentally playing with foreign replica fire (567)

• created set to 2009-08-31 01:38:09
• creator set to spang@bestpractical.com
• original_replica set to e26467b0-95c6-11de-80cb-cdb2d2e3ae72
• content set to Right now, it's not at all obvious that we *expect* a star topology whenever you're using a foreign replica, and it's all too easy to accidentally pull or push to a new foreign replica. We need to make it absolutely clear that SD will become very confused if more than one person is talking to a legacy system and sharing these changes with others. * add --force whenever a user tries to push or pull to a new foreign replica she hasn't pushed or pulled from before, with a scary warning message
• ticket set to ef5b745f-95ce-11de-8278-e221a4bb0ccd

protect users from accidentally playing with foreign replica fire (567)

• owner set to spang@bestpractical.com
• creator set to spang@bestpractical.com
• original_replica set to e26467b0-95c6-11de-80cb-cdb2d2e3ae72
• status set to new
• reporter set to spang@bestpractical.com
• created set to 2009-08-31 01:38:07
• component set to core
• summary set to protect users from accidentally playing with foreign replica fire
• milestone set to diana

publish should check for rsync >= 2.6.7 (495)

• status changed from new to closed

Comment on: publish should check for rsync >= 2.6.7 (495)

• created set to 2009-08-31 01:25:43
• creator set to spang@bestpractical.com
• original_replica set to e26467b0-95c6-11de-80cb-cdb2d2e3ae72
• content set to Closed by git commit 348c4b2029e66118c81365cae993a53f2af18766
• ticket set to 816699d2-918f-11de-811d-a8b61e21f617

Comment on: github sync needs better error checking (564)

• created set to 2009-08-31 01:24:59
• creator set to spang@bestpractical.com
• original_replica set to e26467b0-95c6-11de-80cb-cdb2d2e3ae72
• content set to Also, better messages when the auth fails, or other errors are encountered. After every attempt to connect to GitHub.com via Net::GitHub, we should be checking for errors.
• ticket set to 19685126-95cd-11de-820d-87a4bc1827f6

github sync needs better error checking (564)

• created set to 2009-08-31 01:24:59
• summary set to github sync needs better error checking
• component set to github-sync
• creator set to spang@bestpractical.com
• original_replica set to e26467b0-95c6-11de-80cb-cdb2d2e3ae72
• status set to new
• milestone set to diana
• reporter set to spang@bestpractical.com