On 4/12/17, Ron Aaron <r...@aaron-tech.com> wrote: > I know how I can get the latest version; but I am quite concerned that if I > do update my system, my users will be unable to sync unless they also go > through that process. > > > I don't think it should be the case that I cannot sync to a repo after an > upgrade. Wasn't that the discussion's resolution? >
You can upgrade to Fossil 2.2 and older Fossil 1.x clients can continue to sync as long as you do not check-in any SHA3 artifacts. By default, Fossil does not create SHA3 artifacts. So upgrading to Fossil 2.2 should not change anything. However, we have deliberately started using SHA3 artifacts on Fossil itself, so at this point it is necessary to run Fossil 2.0 or later in order to access the complete Fossil repository. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
