[tahoe-lafs-trac-stream] [tahoe-lafs] #1452: clarify policy about what versions of dependencies Tahoe-LAFS requires

[tahoe-lafs]

#1452: clarify policy about what versions of dependencies Tahoe-LAFS requires
-------------------------+-------------------------------------------------
     Reporter:  zooko    |      Owner:  somebody
         Type:  defect   |     Status:  new
     Priority:           |  Milestone:  soon (release n/a)
  critical               |    Version:  1.8.2
    Component:           |   Keywords:  packaging setuptools exocet testing
  packaging              |
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by gdt):

 This ticket conflates two issues: how to get test/buildbot coverage over
 all possible set of legitimate dependencies, and what to express in
 policy.  I think the policy issues are pretty standard and
 straightforward:

 A dependency package's version has two separate constraints:
  * minimum version M, below which reports of trouble are summarily closed
 as WONTFIX
  * frequently tested version T, below which there might be trouble because
 of lack of testing
  * (possibly) highest version H believed to work, because >H is too
 bleeding edge

 The response to a problem with x, M <= x < T, would be to take a clean
 patch if it doesn't break anything, maybe to spend a few minutes thinking
 about it, and maybe to incrnease M to higher than X.

 M should always be a version that's been released for a year, absent
 special circumstances, one of which is that it's comaintained with trac
 and not used by much of anything else.


 Beyond that, sure it would be great if there were buildbots that install
 various versions of dependencies.

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