HeidiSQL nightly builds
-
- Posts: 12
- Joined: Fri Feb 24, 2023 5:13 pm
HeidiSQL nightly builds
HeidiSQL releases nightly builds that show up as the current version in SUMo. It seems the developer's versioning scheme is that the build number (major.minor.patch.build) is incremented for nightly releases and each new release version updates the minor and/or major version (I have not seen any patch releases, but I suppose it's possible). Is there a current solution for how to only mark official releases as official updates other than reporting each nightly as beta? I know I can skip an update, but that only works until the next nightly is released.
-
- Site Admin
- Posts: 1630
- Joined: Sun Jul 03, 2011 8:13 pm
-
- Posts: 12
- Joined: Fri Feb 24, 2023 5:13 pm
Re: HeidiSQL nightly builds
Thanks. I can see the correct version marked as current now.
-
- Site Admin
- Posts: 1630
- Joined: Sun Jul 03, 2011 8:13 pm
Re: HeidiSQL nightly builds
Perfect.
-
- Posts: 12
- Joined: Fri Feb 24, 2023 5:13 pm
Re: HeidiSQL nightly builds
A new nightly build of HeidiSQL has come out and is marked as current in SUMo. Does each nightly build need to be manually reported as beta or is there some other way to handle this automatically?
-
- Site Admin
- Posts: 1630
- Joined: Sun Jul 03, 2011 8:13 pm
Re: HeidiSQL nightly builds
Manual fixed on my side, so reporting here is welcome.DustinLuck wrote: ↑Fri Mar 31, 2023 4:06 pm A new nightly build of HeidiSQL has come out and is marked as current in SUMo. Does each nightly build need to be manually reported as beta or is there some other way to handle this automatically?
Now fixed, thanks !
-
- Posts: 12
- Joined: Fri Feb 24, 2023 5:13 pm
Re: HeidiSQL nightly builds
Are you open to feature requests? If so, what's the best way to make a request? If this is an appropriate place, my idea is below.
Request: Add a skip update option to the interface that would allow skipping all updates until a particular portion of the application's version changes (major/minor/patch/build). This will allow more flexibility for users to decide what level of change they want to be notified of. In the case of HeidiSQL, I'd use this feature to skip all new versions until the patch or higher level of the revision is greater than my installed version.
Request: Add a skip update option to the interface that would allow skipping all updates until a particular portion of the application's version changes (major/minor/patch/build). This will allow more flexibility for users to decide what level of change they want to be notified of. In the case of HeidiSQL, I'd use this feature to skip all new versions until the patch or higher level of the revision is greater than my installed version.
-
- Site Admin
- Posts: 1630
- Joined: Sun Jul 03, 2011 8:13 pm
Re: HeidiSQL nightly builds
Thanks !
Already on the ToDo list : https://www.kcsoftwares.com/bugs/view.php?id=4786
Already on the ToDo list : https://www.kcsoftwares.com/bugs/view.php?id=4786
-
- Posts: 12
- Joined: Fri Feb 24, 2023 5:13 pm
Re: HeidiSQL nightly builds
Ah, yes. I see my issue would be handled by use case d. I also see this has been open for 5 years which tells me it's probably very low on the priority list. Even so, this is a minor inconvenience, and the value of the software as-is means I'm still better off having found it.
Thanks for a great tool!
Thanks for a great tool!
-
- Site Admin
- Posts: 1630
- Joined: Sun Jul 03, 2011 8:13 pm
Re: HeidiSQL nightly builds
Thanks ! Indeed a good idea, but i'm not sure many users would actively use it. Let's see if some others "up vote" for this one !