linuxdeployqt
linuxdeployqt copied to clipboard
probonopd
Versionize linuxdeployqt
Hello,
Recently in #35 we saw that there was somewhat of a regression, which brings us to the versioning question.
Why not do releases? I know this is probably because of the "This may not be fully working yet" disclaimer, but having versions would allow us to use a specific working version instead of "continuous" which can break from time to time.
Yes, you are right. Reasons are: Things are still "moving" (so technically speaking we are still in 0.x.x), and releasing takes time and effort. Most likely I'd do time-based (automated) releases if I find a script that automate it.
Yeah time-based releases would be ok. Maybe a quarterly scheme would be appropriate, compute what's best based on the number of commits.
I encountered problems with continuous few times breaking my builds. I use it because there are only binaries for continuous on GitHub releases page. It would be good to have other not changing releases to make depending project builds more reproducible.
Agree... anyone volunteers to be the Release Manager?
Sorry but what should a Release Manager specifically do for the repository? I'd like to be a volunteer : )
@goolhanrry: a release manager tag versions and usually keeps a changelog up to date.
Just chiming in to say that I am very interested on this. I personally do not need changelogs, actual version numbers or anything fancy. I just want to be able to "pin" a specific commit so things do not break magically out of my control.
