Changes between Initial Version and Version 1 of Ticket #1452


Ignore:
Timestamp:
2011-07-28T04:09:16Z (13 years ago)
Author:
zooko
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1452 – Description

    initial v1  
    1 There are conflicting ideas about how tight the requirements Tahoe-LAFS should place on dependencies (in [source:src/allmydata/_auto_deps.py]). One way to do it would to be require versions of dependencies which we know work with Tahoe-LAFS (i.e. they don't have any critical bugs that are triggered by the way Tahoe-LAFS uses them nor fatal incompatibilities with Tahoe-LAFS or other code that Tahoe-LAFS uses). This would be the tightest policy. The other extreme—the loosest policy—is to allow any version unless we know for sure that particular version has a critical bug or incompatibility.
     1There are conflicting ideas about how tight to make the requirements Tahoe-LAFS should place on dependencies (in [source:src/allmydata/_auto_deps.py]). One way to do it would to be require versions of dependencies which we know work with Tahoe-LAFS (i.e. they don't have any critical bugs that are triggered by the way Tahoe-LAFS uses them nor fatal incompatibilities with Tahoe-LAFS or other code that Tahoe-LAFS uses). This would be the tightest policy. The other extreme—the loosest policy—is to allow any version unless we know for sure that particular version has a critical bug or incompatibility.
    22
    33I personally find it a bit dubious if we specify that Tahoe-LAFS requires a version of {{{Package X}}} greater than or equal to {{{Version N}}}, if we don't have any buildbots that have {{{Version N}}} installed. To me that sounds like we are claiming that Tahoe-LAFS will work with {{{Version N}}} of {{{Package X}}}, but making that claim without reproducible evidence that it is true. On the other hand we can just rely on the absence of any bug reports from the field which can be traced to a bug or incompatibility in some version of one of our dependencies.