Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding a more recent release #550

Open
interrogator opened this issue Mar 30, 2018 · 8 comments
Open

Adding a more recent release #550

interrogator opened this issue Mar 30, 2018 · 8 comments

Comments

@interrogator
Copy link

Is there any chance we can get a more recent release here on GitHub? The last one is from 2016. Alternatively, is there another place where releases can be authoritatively tracked?

@jl777
Copy link
Owner

jl777 commented Mar 30, 2018

https://github.com/jl777/komodo/tree/dev

dev branch is where all the changes are happening for the komodod, the master branch is only updated unless there is a critical bug or forking change needed so the fewer in master the better.

https://github.com/jl777/SuperNET/tree/dev is where all the barterDEX core (marketmaker) development is merged into

These are the two main places for the core level changes. All of the GUI development happens in the GUI repos.

@interrogator
Copy link
Author

OK, thanks for the clarification. So https://github.com/jl777/komodo/releases will only be updated when master is updated?

In our workflow we'd like to be able to check when updates to komodod are available, even if minor, via versioning. How would you recommend we find out the version at a given moment (preferably without pulling the source)?

@jl777
Copy link
Owner

jl777 commented Apr 5, 2018

I guess when the dev branch is updated, those are experimental but at least not known to crash type of updated.

the beta branch is released after dev branch is deemed stable

I think git might have a way to check the latest git hash for each branch? not sure the best way as this is out of my expertise

@interrogator
Copy link
Author

Should I ask on Slack if any other contributors want to handle the process of making new tags/releases on GitHub? The guy who makes the windows and and OSX packages could probably do it? This person could take important dev branch updates with minor versions (e.g. 1.0.8rc1 or whatever), and any stable updates could get a numerical bump (1.0.9 or whatever).

Basically, at the moment, we aren't sure which is the newest stable release, newest release, and where the version info is stored for these.

@jl777
Copy link
Owner

jl777 commented Apr 5, 2018

we are making so many dev branch updates, the release management is not in place. There could be dozens of new dev branch releases in a week. beta is a lot more stable, with master being for serious bugs/hardforking changes.

Since komodod is just one component for the full release of GUI, barterDEX, agama, any release tagging would likely be done by the release packagers. there is an automated build process for many components. I will ask for others more familiar with it to post details here

@himu007
Copy link

himu007 commented Apr 5, 2018

Hi @interrogator, please find links to the latest binaries from this link below.
https://github.com/KomodoPlatform/KomodoPlatform/wiki/Source-of-all-KomodoPlatform-Repositories-and-Releases

@interrogator
Copy link
Author

Hey, awesome, thanks for providing links to those. That's definitely a start, but as you can see from that page, nowhere is the current version listed, so there is no way for us to know whether or not we need to upgrade without downloading and probably installing.

As said above, using GitHub releases is really designed for this purpose --- but if you can't do that for some reason, would you be able to add the version information to the various downloads available at: https://github.com/KomodoPlatform/KomodoPlatform/wiki/Source-of-all-KomodoPlatform-Repositories-and-Releases

@jl777
Copy link
Owner

jl777 commented Mar 20, 2019

mandatory updates are in master, so if you just do a git pull and nothing new comes, then there is no need to update

miketout pushed a commit to miketout/VerusCoin that referenced this issue Nov 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants