On 7/26/2018 7:46 PM, Warren Young wrote:
On Jul 26, 2018, at 7:28 PM, Ryan Noll (Mailing List)
<rnoll.li...@bubbaboy.net> wrote:
I upgraded via source to 2.6 (fd3198322a 2018-07-25 13:20:15 UTC)
Unless you need one of the changes between the 2.6 release made in early May
and the current trunk, I’d recommend staying on release versions until the
current trunk stabilizes:
$ fossil up release
That’s a tag, not a branch name, so it’s a temporary repositioning. That is,
if you say “fossil up” again, you’ll get fast-forwarded to the tip of trunk, so
if you want to stay on release versions, you’ll have to remember to say “fossil
up release” every time.
Normally Fossil trunk is pretty stable at all times, but at the moment, there
are big changes afoot, so unless you plan to test and/or use those new
features, I think it’s best to stick to the current release.
Thank you for the clarification, as I was not sure exactly how to
describe the version that I had upgraded to. Also, I was unaware of
"fossil up release" until I took a closer look at the "fossil help up"
output and tags.
Thanks for the hints, now I can incorporate that knowledge to my
projects that utilize fossil.
-Ryan
_______________________________________________
fossil-dev mailing list
fossil-dev@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
