Closed rettinghaus closed 5 years ago
Dear Klaus,
Thanks for the remark. We will make named releases whenever we deploy stable versions, and when relevant add a note. That will definitely make it easier for people to avoid what is unstable.
Again thanks for a valid remark
Yours
Sigfrid
On Thu, 6 Sep 2018 at 17:50, Klaus Rettinghaus notifications@github.com wrote:
To better keep track of development, it would be good to have release points, see GitHub (pre-) releases and tags. Especially because the front end didn't change it look since the start, it would be good to have an indicator somewhere, showing which version is in productive use.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Det-Kongelige-Bibliotek/MerMEId/issues/142, or mute the thread https://github.com/notifications/unsubscribe-auth/ACf_KA0esSq5YT9e7Hz3CrjLsTSL1B3Xks5uYUQwgaJpZM4WdORg .
-- Sigfrid Lundberg, Ph.D., System developer Lund, Sweden http://sigfrid-lundberg.se/
Yes, good point. It's been on my mind for some time. There are revision numbers but they are not immediately visible. And they do not distinguish minor and major revisions, nor do they mark stable releases. I was planning to make a major release point just before we will (hopefully) be upgrading to MEI 4.0.0, but since the new MEI release is delayed we may want to have some tags before that. We are close to a point where such a tag would be relevant. In a couple of weeks, I hope. Just have to finish a few things.
To better keep track of development, it would be good to have release points, see GitHub (pre-) releases and tags. Especially because the front end didn't change it look since the start, it would be good to have an indicator somewhere, showing which version is in productive use.