On 2/28/17, Richard Hipp <d...@sqlite.org> wrote: > > release Fossil 2.0 and Fossil 2.1 simultaneously. The only difference > between these two version will be that Fossil 2.0 still always > generates SHA1 hashes on new content whereas Fossil 2.1 generates only > SHA3 hashes. But both version understand SHA3 hashes.
Fossil 2.2 will reject any new content with a SHA1 hash name, except when doing a clone. So there is now a three-phase rollout: (1) Begin deploying Fossil 2.0. Wait until everyone has upgraded. (2) Begin deploying Fossil 2.1. Wait until everyone has upgraded and synced up. (3) Begin deploying Fossil 2.2. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
