Fossil

Check-in [9d673f04]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Updated the Debian Stretch speculation bit at the end of the hashpolicy document with latest results from the forum thread.
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 9d673f04f5a9ce41b563b3fa365e937c1dde61b327175b2acf5c69f8beec4fc5
User & Date: wyoung 2019-01-09 12:31:05
Context
2019-01-10
06:03
Fixed an errant use of a Markdown hyperlink in a Fossil wiki document. check-in: 15cbb09d user: wyoung tags: trunk
2019-01-09
12:31
Updated the Debian Stretch speculation bit at the end of the hashpolicy document with latest results from the forum thread. check-in: 9d673f04 user: wyoung tags: trunk
2019-01-08
19:08
Restore the ability to delete a wiki page. check-in: e947378e user: drh tags: trunk
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to www/hashpolicy.wiki.

   165    165   Of course, if some members of your team stubbornly refuse to upgrade past
   166    166   Fossil 1.37, you should avoid changing the hash policy and creating
   167    167   artifacts with SHA3 names, because once you do that your recalcitrant
   168    168   coworkers will no longer be able to collaborate.
   169    169   
   170    170   <h2>A Pure SHA3 Future</h2>
   171    171   
   172         -At some point in the future, years from now, after everybody has finally
   173         -upgraded to Fossil 2.0 or later, the default hash policy will probably
   174         -change to "sha3", or maybe even "shun-sha1".  By the time that happens,
   175         -you will probably already be using SHA3 on all your projects and so you
   176         -are unlikely to notice.
          172  +At some point in the future, after everybody has finally upgraded to
          173  +Fossil 2.0 or later, the default hash policy will probably change to
          174  +"sha3", or maybe even "shun-sha1".  By the time that happens, you will
          175  +probably already be using SHA3 on all your projects and so you are
          176  +unlikely to notice.
   177    177   
   178    178   This probably won't happen until after all of the operating systems
   179    179   shipping binary versions of Fossil switch to Fossil 2.1 or later. The
   180         -big standout is Debian Stretch (9.0), which is not expected to be
   181         -replaced until March 2019, and it won't fall out of support until June
   182         -2022.  We do not yet know if we will switch the default hash policy
   183         -during that window or not until after Debian 9 is fully out of support.
          180  +big standout is Debian Stretch (v9), since it still ships Fossil 1.37
          181  +due to its stable packages policy. Stretch will be the current release
          182  +version of Debian until "some time mid 2019" according to [the latest
          183  +published release plan][deb10]. Debian Stretch will then remain in
          184  +support until June 2022. We do not yet know if we will switch the
          185  +default hash policy during that window or not until after Stretch is
          186  +fully out of support.
          187  +
          188  +
          189  +[deb10]: https://lists.debian.org/debian-devel-announce/2018/04/msg00006.html