• 0.2.0

    100%
    0 Open
    1 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2007-05-02 07:00:00 +00:00
  • 0.3.0

    100%
    0 Open
    3 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2007-05-11 07:00:00 +00:00
  • 0.5.0

    100%
    0 Open
    19 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2007-08-17 07:00:00 +00:00
  • 0.5.1

    100%
    0 Open
    1 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2007-08-23 21:03:15 +00:00
    • resolve the XSRF web-based security attacks
  • 0.6.0

    100%
    0 Open
    18 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2007-09-24 21:43:58 +00:00

    release focus:

    • packaging
    • performance
  • 0.6.1

    100%
    0 Open
    29 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2007-10-15 07:00:00 +00:00

    focus:

    • usability: packaging, documentation
    • usability: CLI
    • performance (nevermind -- performance has been measured and is good enough!)
  • 0.7.0

    100%
    0 Open
    23 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2008-01-08 20:48:15 +00:00

    focus:

    • Small Mutable Distributed Files
    • distributed directories (built on above)
    • correct SHA-256
    • packaging
  • 0 Open
    9 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2008-01-15 08:00:00 +00:00
    • upload helper, resumable uploads, file progress, file deduplication
    • installer (Windows)
    • Windows virtual drive integration, login, service, bootstrap, initial directory
    • web client multiple file upload, file progress
    • usability testing
    • sharing stuff (need more detail)
    • operational grid roll-out
    • 3 1 adding meta data to directory edges (eg. file size, timestamp)

    No's

    • no tiny url
    • no backups
  • 0 Open
    12 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2008-03-11 07:00:00 +00:00
    • backup client (existing or new client)
    • tiny url for sharing (not implemented)

    No's

    • no sharing revocation, time limits
    • do not need current upload/download manager
    • not necessary to have backups accessible from web (yet)
    • no quota (yet)
    • no file checking/repair/rebalance (yet)
    • no bandwidth shaping (not necessary with all data being tunneled over one link
  • 1.0.0

    100%
    0 Open
    4 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2008-03-25 21:03:26 +00:00
  • 1.1.0

    100%
    0 Open
    44 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2008-06-11 07:00:00 +00:00
    • new mutable upload/download code (faster and safer and better tested)
    • fix bug in uploading large directories
    • packaging/testing improvements to fix the problem of using buggy pycryptopp-0.3.0 with Tahoe
    • more ?
  • 1.2.0

    100%
    0 Open
    8 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2008-07-21 07:00:00 +00:00
    • Fix security bug #491
    • Release all trunk changes up to this point.
  • 1.3.0

    100%
    0 Open
    49 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2009-02-14 00:05:56 +00:00

    Release focus: checker/verifier/repairer:

    • checking: just count number of available shares

    • verifying: read share contents, check hashes

    • repair: create new shares as necessary to replace bad/missing ones.

      • Mutable shares are repaired in place. Note that mutable repair requires
        a write-cap, to make sure the write-enabler shared secrets are created
        correctly. It would be nice to be able to repair from just a read-cap or
        a verify-cap, but this may need to wait until we switch to DSA mutable
        files, and/or change the way we control server-side write access.
      • Immutable shares must be manually deleted from the storage servers, so
        repair needs a mechanism to report which shares should be examined and
        removed. Immutable repair really means creating new shares to make up
        for the bad ones.
    • there should be a "check" button for each file to initiate a check, or a
      verify, with or without auto-repair. The page that this button displays
      should contain the results of the operation: which shares were found
      where, how much verification was performed, whether repair was deemed
      necessary, whether repair was actually done, and the success or failure of
      the repair operation.

    • there should be a "deep-check" button for each directory to perform a
      recursive traversal and check/verify/repair everything reachable from that
      point. The page this returns should show aggregate information about the
      check/repair: a count of how many files/dirs were examined, how many were
      healthy, how many had problems, etc. The page should have a line or two
      about each problem.

    • there should be machine-parseable versions of these buttons: POST
      operations that return JSON with the same information as the
      human-targetted HTML described above.

    • serious problems (like hash failures) should be automatically reported to
      some centralized Incident Gatherer, so we can discover bugs, failing
      drives, or malice.

    • allmydata should be able to run a periodic checker/repairer on customer
      rootcaps. We should be able to count the number of missing/bad shares and
      track it over time (to inform us of the impact of bouncing/moving storage
      servers, discover failing drives, etc). We need to find out how long the
      full check/verify/repair process takes, so we can decide upon a suitable
      repeat rate (perhaps once a month).

    • to handle bad immutable shares, we should add a 'tahoe check-share'
      command that can be run on the storage-server side and check all the
      hashes of a single share file on disk. If file-verify observes a bad hash,
      we should be able to go to the disk and use this tool to see if the
      problem is transient or persistent, to make decisions about the stability
      of that disk.

  • 1.4.1

    100%
    0 Open
    13 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2009-04-13 00:00:00 +00:00

    Garbage collection, and several improvements in diagnostics, monitoring, error-reporting, ui, and documentation. See also this thread:

    http://allmydata.org/pipermail/tahoe-dev/2009-March/001381.html

  • 1.5.0

    100%
    0 Open
    34 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2009-08-02 05:34:48 +00:00
    • new WUI style
    • remove limit on size of mutable files
    • prepare for inclusion in distributions such as Debian, Fedora, Gentoo, Ubutu, Nexenta
    • port to more platforms, which means promoting these builders from Unsupported to Supported:
    • ARM CPU and embedded devices: "Zandr Lenny-armel" and "François Lenny-armv5tel"
    • Fedora: Ruben Fedora
    • !ArchLinux: Dan !ArchLinux
    • OpenBSD/sparc64: Ben OpenBSD-sparc64
    • fix bugs
  • 1.6.0

    100%
    0 Open
    50 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2010-02-02 06:11:25 +00:00
    • immutable directories
    • faster download
    • backup uses immutable directories
    • many usability improvements
    • fuse works again
    • many smaller bugfixes and improvements
  • 1.6.1

    100%
    0 Open
    7 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2010-02-27 23:59:59 +00:00
    • fix any regressions introduced in 1.6.0
    • any other bugfixes (small, narrow, not-a-new-feature)
  • 1.7.0

    100%
    0 Open
    50 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2010-06-19 06:40:02 +00:00
    • servers of happiness
    • SFTP front-end
    • unicode support
    • auto-code-coverage reports
  • 1.7.1

    100%
    0 Open
    14 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2010-07-19 04:08:40 +00:00
    • bugfixes
    • packaging improvements
    • usability improvements

    http://tahoe-lafs.org/pipermail/tahoe-dev/2010-June/004567.html

    tagged: [changeset:7e8bb7339109c8c7]

  • 1.8β

    100%
    0 Open
    15 Closed
    Updated 2024-09-18 09:10:07 +00:00
    Closed 2010-08-03 04:46:18 +00:00