[tahoe-lafs-trac-stream] [tahoe-lafs] #1292: 'tahoe rm' without a path gives an AssertionError with no explanation

tahoe-lafs trac at tahoe-lafs.org
Fri Jan 21 22:08:19 UTC 2011


#1292: 'tahoe rm' without a path gives an AssertionError with no explanation
-----------------------------------+----------------------------------------
     Reporter:  davidsarah         |       Owner:  warner                                                 
         Type:  defect             |      Status:  new                                                    
     Priority:  major              |   Milestone:  1.9.0                                                  
    Component:  code-frontend-cli  |     Version:  1.8.1                                                  
   Resolution:                     |    Keywords:  error usability tahoe-rm docs easy docs-needed reviewed
Launchpad Bug:                     |  
-----------------------------------+----------------------------------------

Comment (by warner):

 Hmmm. I'm happy to have docs get fixed or added after the code freeze, but
 I'm not excited about landing a code change which explicitly references a
 missing piece of documentation. I wouldn't want to ship this change
 without the docs, and given the non-trivial challenge of explaining what
 "delete" means in an object-graph FS to a traditional-FS audience, I'm not
 confident that the documentation will appear before the release. And then
 I'd be faced with deciding between yanking the code change on the day of
 the release (way after code freeze) vs shipping with an embarassing
 dangling docs-pointer.

 Once we get the docs, the release manager may choose to accept the patch
 during freeze (it is pretty small, after all).

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1292#comment:10>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage


More information about the tahoe-lafs-trac-stream mailing list