Re: I have cleaned Leo's branches and updated info issue #1058

2022-03-27 Thread Edward K. Ream
On Sun, Mar 27, 2022 at 1:52 PM Viktor Ransmayr wrote: However now the next important step is the release of Leo 6.6. > Right. All new work will be assigned for the 6.6.1 release, and each issue must have its own PR. Edward -- You received this message because you are subscribed to the Google

Re: I have cleaned Leo's branches and updated info issue #1058

2022-03-27 Thread Viktor Ransmayr
Hello Felix, Am So., 27. März 2022 um 20:11 Uhr schrieb Félix : > Salutations Viktor, > > The felix-server4 branch is specifically where I push development progress > for the 'leoserver.py' file in leo/core. > > Indeed, most of the time it is equal to 'devel', but when I'm working on > new server

Re: I have cleaned Leo's branches and updated info issue #1058

2022-03-27 Thread Félix
Salutations Viktor, The felix-server4 branch is specifically where I push development progress for the 'leoserver.py' file in leo/core. Indeed, most of the time it is equal to 'devel', but when I'm working on new server features, that's the branch where you can see and test those new server f

Re: I have cleaned Leo's branches and updated info issue #1058

2022-03-27 Thread Viktor Ransmayr
Hello Edward & Felix, Am So., 27. März 2022 um 14:19 Uhr schrieb Edward K. Ream < edream...@gmail.com>: > Leo's Github branch page > now contains only > three branches: master, devel and felix-server4. All three branches are > protected. None ca

Re: 6.6 coming this Thursday, March 31

2022-03-27 Thread Viktor Ransmayr
Hello Edward, Am So., 27. März 2022 um 19:31 Uhr schrieb Edward K. Ream < edream...@gmail.com>: > > On Sun, Mar 27, 2022 at 11:09 AM Viktor Ransmayr < > viktor.ransm...@gmail.com> wrote: > > > Do you still plan to create a release candidate & upload it to PyPI > before? > > No. The present plan

Re: 6.6 coming this Thursday, March 31

2022-03-27 Thread Edward K. Ream
On Sun, Mar 27, 2022 at 11:09 AM Viktor Ransmayr wrote: > Do you still plan to create a release candidate & upload it to PyPI before? No. The present plan is to upload 6.6 (final) to PyPI on Thursday. Edward -- You received this message because you are subscribed to the Google Groups "leo-e

Re: 6.6 coming this Thursday, March 31

2022-03-27 Thread Viktor Ransmayr
Hello Edward, On Sun, 27 Mar 2022, 14:03 Edward K. Ream, wrote: > Leo 6.6 is code complete. Absent something completely unexpected, Leo 6.6 > final will go out the door this Thursday, March 31. Do you still plan to create a release candidate & upload it to PyPI before? With kind regards Vikt

I have cleaned Leo's branches and updated info issue #1058

2022-03-27 Thread Edward K. Ream
Leo's Github branch page now contains only three branches: master, devel and felix-server4. All three branches are protected. None can be deleted. I have deleted all other branches, including all release branches. Leo's Github release page

6.6 coming this Thursday, March 31

2022-03-27 Thread Edward K. Ream
Leo 6.6 is code complete. Absent something completely unexpected, Leo 6.6 final will go out the door this Thursday, March 31. In the meantime, please test devel. Thanks. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe fro

Re: Please test devel and PR #2523

2022-03-27 Thread Edward K. Ream
On Sat, Mar 26, 2022 at 7:44 PM Félix wrote: > Hello Leonistas! 🦁 > > I've tested, no errors found, and I've made a last pr 2526 for the server > to go along with it. And I'll be coding with that through the week before > release, to see if any bugs remain when using it in real world instead of