Gabor Szots wrote: ↑Thu Jun 22, 2023 4:11 pm
In the last day you have relased and deleted 3 or maybe 4 versions. This certainly won't improve their chances to be tested. I have put 2.17.08 in my testing queue but now that you have deleted it and released 2.17.09 instead I am not so enthusiastic any more.
hi,
I am really sorry to hear that. Let me explain. I first made a new release 2.17.08, but I am not expert in github, I put the new sources after(. So I deleted it. I can't remember, but I had perhaps made another delete. Finally I made the right 2.17.08.
Then this morning I looked by chance at the quiescence routine, and thought about a modification. To my surprise, it gained about 20 elo. So I decided to made this new release.
ok, no matter what I find, I will stay with this release for some time.
I will wait to gain at least 100 points. but it is becoming more and more difficult. I am also trying to develop a tuner, but it is more complex that what I thought.
Philippe
No problem Philippe. Just go at the pace which suits you best.
As things stand the next time I'm going to launch a new tournament is no sooner than Saturday which means you still have time to think things over. I'm going to test the version which is at your site by the week-end.
Gabor Szots wrote: ↑Thu Jun 22, 2023 4:11 pm
In the last day you have relased and deleted 3 or maybe 4 versions. This certainly won't improve their chances to be tested. I have put 2.17.08 in my testing queue but now that you have deleted it and released 2.17.09 instead I am not so enthusiastic any more.
hi,
I am really sorry to hear that. Let me explain. I first made a new release 2.17.08, but I am not expert in github, I put the new sources after(. So I deleted it. I can't remember, but I had perhaps made another delete. Finally I made the right 2.17.08.
Then this morning I looked by chance at the quiescence routine, and thought about a modification. To my surprise, it gained about 20 elo. So I decided to made this new release.
ok, no matter what I find, I will stay with this release for some time.
I will wait to gain at least 100 points. but it is becoming more and more difficult. I am also trying to develop a tuner, but it is more complex that what I thought.
Philippe
I'm not sure what you mean by "put the new sources after", but generally you should never have to full delete a "release". You can always edit it and you can delete and create new tags. If you messed up the actual version tag, you can always delete the tag and then create a new one. If you uploaded the wrong files, you can always just edit the release and replace them.
But once you have a release, you should never delete it. If you make changes to the code, whether it's bug fixes, new features, whatever, don't update/delete/modify any existing release. It's a new release.
What I did was , first I created a new release, with a new tag. Then I put the new sources on github. But I noticed that in the assets of this new release the source were those of the ancient release. Its why I deleted the release. I didn't found a way to have in the assets the new sources. But as I said, Im not an expert, not even a good user.
Could you explain me the right thing to do ?
Thanks for your help.
That is probably because you are using Arena. Clover now uses FRC notation for castle moves (e1h1, e1a1, e8h8, e8a8) which aren't accepted by Arena, but are accepted by most other GUIs, like CuteChess. I suggest switching to CuteChess if you want to test Clover or just wait until I quickly replace the binaries of 5.0 with this fix
That is probably because you are using Arena. Clover now uses FRC notation for castle moves (e1h1, e1a1, e8h8, e8a8) which aren't accepted by Arena, but are accepted by most other GUIs, like CuteChess. I suggest switching to CuteChess if you want to test Clover or just wait until I quickly replace the binaries of 5.0 with this fix
I have now updated binaries for the Clover 5.0 release, should print correctly for Arena. Thanks for reporting!
