Replies: 0 comments 7 replies
-
Hi, I'll rebuild a fresh version for you ;) |
Beta Was this translation helpful? Give feedback.
-
thank you @RoiArthurB but instead of having you doing it manually I though the idea was to have an automatic process (maybe not every commit but let's say every day)? Am i wrong? What is the process though github UI to do it so i don't have to bother you too much? |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
I agree with Arthur, exactly what i was writing |
Beta Was this translation helpful? Give feedback.
-
Ok thank you Arthur for the release I'll test it. I also understantd now how to generate one (I was indeed missing the point 4 and using the master) I also agree with you if we have an instable version it's tricky to generate one everyday (unless we clearly specify it's the current version) but that's a long discussion. After for me there is 3 kind of user:
Thank for the very quick answer ! |
Beta Was this translation helpful? Give feedback.
-
for 2: yes, but this kind of user also should base on a more stable version than "alpha", otherwise there will be many new issue :) |
Beta Was this translation helpful? Give feedback.
-
(converting the issue to a discussion as it seems more appropriate to discuss how to release GAMA and for whom :) ) |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
Is seems that the automatic release production is broken. The last release available is from 25_021_22 and it now 42 commits ahead from the master
The travis workflow (https://github.com/gama-platform/gama/actions) seems to be called everyday and looks good (green) but the release is not pushed/produced here
https://github.com/gama-platform/gama/releases/tag/1.8.2
Beta Was this translation helpful? Give feedback.
All reactions