Re: Leo 6.8.0 b1 will be delayed at least one week

2024-05-30 Thread Edward K. Ream
On Thu, May 30, 2024 at 3:02 PM Thomas Passin wrote: > > On Thursday, May 30, 2024 at 3:13:39 PM UTC-4 Edward K. Ream wrote: > > My concern is simple: I don't want to release *anything *until we all > test the "devel" branch more thoroughly. > > > Don't we want to be testing the 6.8.0 branch at t

Re: Leo 6.8.0 b1 will be delayed at least one week

2024-05-30 Thread Thomas Passin
On Thursday, May 30, 2024 at 3:13:39 PM UTC-4 Edward K. Ream wrote: My concern is simple: I don't want to release *anything *until we all test the "devel" branch more thoroughly. Don't we want to be testing the 6.8.0 branch at this time, instead of the devel branch? -- You received this me

Re: Leo 6.8.0 b1 will be delayed at least one week

2024-05-30 Thread Edward K. Ream
On Thu, May 30, 2024 at 1:33 PM Viktor Ransmayr wrote: >> Nevertheless, I think an extra week of testing is still justified. Leo's devel branch is working w/o any (immediate) issues for me in a Debian > 12 & Fedora 39 VM ! > > From my POV the advantage of this beta would have been to also get an

Re: Leo 6.8.0 b1 will be delayed at least one week

2024-05-30 Thread Viktor Ransmayr
Hello Edward, Edward K. Ream schrieb am Donnerstag, 30. Mai 2024 um 13:04:30 UTC+2: On Thursday, May 30, 2024 at 5:43:12 AM UTC-5 Edward K. Ream wrote: Thomas has just discovered a serious recent error in Leo's read code. See #3957 . The fi

Re: Leo 6.8.0 b1 will be delayed at least one week

2024-05-30 Thread Edward K. Ream
On Thu, May 30, 2024 at 7:12 AM Thomas Passin wrote: > My concern was that the statement had intended to be an assignment but by mistake did nothing. I'm so glad you found the do-nothing statement while I still had some memory of the issues involved. The big three checkers: pylint, ruff, and myp

Re: Leo 6.8.0 b1 will be delayed at least one week

2024-05-30 Thread Thomas Passin
On Thursday, May 30, 2024 at 7:04:30 AM UTC-4 Edward K. Ream wrote: On Thursday, May 30, 2024 at 5:43:12 AM UTC-5 Edward K. Ream wrote: Thomas has just discovered a serious recent error in Leo's read code. See #3957 . The fix may be straigh

Re: Leo 6.8.0 b1 will be delayed at least one week

2024-05-30 Thread Edward K. Ream
On Thursday, May 30, 2024 at 6:04:30 AM UTC-5 Edward K. Ream wrote: PR #3958 simply removes a do-nothing statement and relocates a comment. I've merged this PR into devel. Edward -- You received this message because you are subscribed to th

Re: Leo 6.8.0 b1 will be delayed at least one week

2024-05-30 Thread Edward K. Ream
On Thursday, May 30, 2024 at 5:43:12 AM UTC-5 Edward K. Ream wrote: Thomas has just discovered a serious recent error in Leo's read code. See #3957 . The fix may be straightforward, but it must be tested for at least one week. Still true. H

Leo 6.8.0 b1 will be delayed at least one week

2024-05-30 Thread Edward K. Ream
Thomas has just discovered a serious recent error in Leo's read code. See #3957 . The fix may be straightforward, but it must be tested for at least one week. Edward -- You received this message because you are subscribed to the Google Grou

Re: Using git-diff Commands

2024-05-30 Thread Edward K. Ream
On Wed, May 29, 2024 at 5:04 PM Thomas Passin wrote: This command, the one to compare two revspecs, turned out not to work for > me. ... > So I reworked the command and its supporting methods. > A worthwhile project. Please keep us all informed. I'll be happy to look at a PR. Edward -- You