Release policies #564
Replies: 4 comments
-
I would vote for the first or second option (or a combination of both). I don't see a reason for us to release every month right now considering our long-term plans and user base. |
Beta Was this translation helpful? Give feedback.
-
OK, let's have a meeting next week when Victor is back and discuss 0.5.0. We probably should start using the 'milestone' option in github, I've started one for 0.0.5 here: https://github.com/gammasim/simtools/milestone/3 |
Beta Was this translation helpful? Give feedback.
-
I agree that defining the milestones and releasing after them is a good idea. Although not too important, I think that the version number does indeed deliver a subtle message on how developed the code is. Therefore, I agree with releasing more often |
Beta Was this translation helpful? Give feedback.
-
I am converting this into a discussion, it is not an issue. |
Beta Was this translation helpful? Give feedback.
-
We have very few releases of simtools, although a lot of development is going on.
Last release 0.4.0 was in November 2022 (https://github.com/gammasim/simtools/releases).
I would suggest that we start thinking about a release policy.
Something to discuss in a meeting.
Beta Was this translation helpful? Give feedback.
All reactions