On Fri, 18 Oct 2013 17:19:55 +0200, Richard Hipp <[email protected]> wrote:
On Fri, Oct 18, 2013 at 11:11 AM, Ben Summers <[email protected]> wrote:
Since it looks like 1.28 is going to be out soon, I'll wait for that
before updating the server.
Why wait? If you look at the bottom of the page for the self-hosting
Fossil server at http://www.fossil-scm.org/fossil/timeline you'll see
that
it is running the latest trunk (or nearly so). Likewise
http://www.sqlite.org/src/timeline and
http://core.tcl.tk/tcl/timelinethough the latter normally lags
slightly behind.
Tip of trunk is almost always working great. When it has issues, they
are
obscure. And the self-check logic (
http://www.fossil-scm.org/fossil/doc/tip/www/selfcheck.wiki) protects
your
repository from damage even on those rare occasions where tip of trunk is
dodgy.
in this case (I don't have any doubts, personally): would it not be
feasible to make the next-to-tip binaries fossil is using itself available
for download in addition to the "release" versions for all users not
compiling themselves? I'm not talking about recompiling every 5 minutes,
but anything faster than the release cycle would help here. this would
help getting recent improvements (such as handling of default user after
clone and timeline reformatting) available rapidly.
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
