On Fri, Oct 18, 2013 at 5:36 PM, j. van den hoff <[email protected]>wrote:
> 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. > The release binaries, because they tend to be long-lived (people still report problems against v1.24[1]) and end up in package repos, go through a much more rigorous test/check/release process which wouldn't be feasible to do on a rapid basis. Just running, e.g. "fossil rebuild" through valgrind can take many hours on a slower machine. The majority of us work directly from the trunk (or a branch kept in sync with it), and releases tend to be made once either the changelog list gets really long or something really important has been fixed (e.g. the recent sqlite3/stderr/assert corner case). [1] i saw a G+ post today where Linus Torvalds calls kernel 3.9 "ancient". My box has 3.2. https://plus.google.com/102150693225130002912/posts/GqUgcYcfQuV -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
