On Feb 28, 2017, at 8:11 AM, Richard Hipp <d...@sqlite.org> wrote: > > (3) All new content added to the repository (for example by "fossil > commit") uses a SHA3-256 hash.
That is a brave step, one I resisted suggesting, but it’s probably for the best. Defaults matter. If the default is SHA-1, we’ll still be looking at Fossil repos storing only SHA-1 hashed artifacts for many years to come, even among those of us who always run recently-built Fossil executables. > (4) There are no hash options. Again, probably for the best. Fewer configurables means fewer things to think about. It also prunes the test space. > (5) Older versions of Fossil will still be able to read the repository > after new SHA3 content has been entered, but the older Fossils will > not understand the new content and won't display it. If you "fossil > push" or "fossil pull" or "fossil clone" then the remote side should > also be Fossil 2.0 or later so that the new SHA3 hashes can be > understood. So if I have a Fossil 1.x client and a Fossil 2.x server and I start adding SHA3-hashed content to it on 2017-04-16 (Easter), the client’s clone will basically be chopped off as if after cloning, they said something like fossil open ~/path/to/repo.fossil 2017-04-16 ? They could roll back to prior releases, but not ever get new updates until they upgrade to Fossil 2? > (6) The only complication to upgrading is that you need to update all > of your fossil (or fossil.exe) binaries to version 2.0 at the same > time. I can get away with that in my own cases. I wonder if you’d share what you plan to do with the SQLite repository? Are you just going to roll to 2.0 immediately after release, and tell people who want to check out the sources via Fossil to upgrade to Fossil 2.0? Or, do you instead plan to continue running Fossil 1.x until the population of Fossil 2 clients reaches some threshold? Have you decided on a backporting plan? That is, will the fossil-2.0 branch be merged into trunk, and no Fossil 1 branch be created, or will Fossil 1 live for some time after Fossil 2.0 is released, with fixes and possibly features backported until some future cutoff date? _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
