forked from bitcoin/bitcoin
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Repo versions, tags, releases and branches #46
Comments
I'm maintaining the darkcoin-git AUR package and I keep the PKGBUILD usually aligned for the bleeding-edge users, sometimes switching branches. As the darkcoin main package should be for regular users, you should stick to tags of the master branch only if possible. |
FornaxA
pushed a commit
to ioncoincore/ion
that referenced
this issue
Jul 6, 2020
…twork e93a698 Update checkpoints to guard against forks in the network (Mitchell Cash) Pull request description: Due to some rumblings about forks in the network, adding some additional checkpoints from what we deem the best chain. Our reasoning is that some known large wallets and all known exchanges are on this chain. Tree-SHA512: 0c28726ed52b0f2f2850c2bd65b8b65eb948fcc3e41e23b7e821d088c20348ae4b47d9481ec297493adbfddfd2f5f363220ee60dda247a691db3fa1b9dbc99e1
FornaxA
pushed a commit
to ioncoincore/ion
that referenced
this issue
Jul 6, 2020
Document outlining upload and download of VM torrents
FornaxA
pushed a commit
to ioncoincore/ion
that referenced
this issue
Jul 6, 2020
Update debian directory for launchpad recipe build Approved-by: Cevap
kwvg
pushed a commit
to kwvg/dash
that referenced
this issue
Dec 21, 2022
* Support initialization callback for thread-local contexts in relic * Make the library thread safe 1. Compile relic with MULTI=PTHREAD to enable thread-local contexts 2. Use core_set_thread_initializer to register an initializer for the thread-local context. Whenever core_get() is called now, the context will be initialized automatically for the current thread (if not already initialized). 3. Remove BLS::Clean. Was never called and is also not useful anymore due each thread having its own context now. 4. Remove AssertInitialized and all calls to it. This is not needed anymore as initialization happens automatically now. 5. Add simple test case to assert that each thread has it's own context
kwvg
added a commit
to kwvg/dash
that referenced
this issue
Dec 21, 2022
…dashpay#46) * build: move sole reference to FetchContent to python-bindings * dashbls: avoid macro conflict by renaming conflicting variable * build: add barebones alternative build system support (GNU Autotools) * build: add support for some definition-based build switches * build: add support for gmp detection and backend * ci: add support for building with GNU Autotools * ci: temporarily drop rdrnd support for autotools builds
knst
pushed a commit
to knst/dash
that referenced
this issue
Nov 5, 2023
…cale{Short,Long}Date 86b1ab6 refactor: Replace deprecated Qt::SystemLocale{Short,Long}Date (Hennadii Stepanov) Pull request description: As all deprecated warning in Qt 5.15.0 were eliminated in dashpay#46, Qt 5.15.1 introduced another one that is fixed in this PR. Required for bitcoin#20182. Details in Qt docs: - https://doc.qt.io/qt-5/qdatetime.html#toString-1 - https://doc.qt.io/qt-5/qdate.html#toString-1 ACKs for top commit: jarolrod: Tested ACK 86b1ab6 on MacOS 10.15.7 and Arch Linux both with Qt 5.15.1 jonasschnelli: Tested ACK 86b1ab6 Tree-SHA512: 1dbba8ee70c895bf58317172a9901cdbe5503b1d6258f51caaae88d88d332d9fbd4697c995192d31e3618ddfd532c5f5881289b3af1184422e5a9263a1224115
knst
pushed a commit
to knst/dash
that referenced
this issue
Nov 6, 2023
…cale{Short,Long}Date 86b1ab6 refactor: Replace deprecated Qt::SystemLocale{Short,Long}Date (Hennadii Stepanov) Pull request description: As all deprecated warning in Qt 5.15.0 were eliminated in dashpay#46, Qt 5.15.1 introduced another one that is fixed in this PR. Required for bitcoin#20182. Details in Qt docs: - https://doc.qt.io/qt-5/qdatetime.html#toString-1 - https://doc.qt.io/qt-5/qdate.html#toString-1 ACKs for top commit: jarolrod: Tested ACK 86b1ab6 on MacOS 10.15.7 and Arch Linux both with Qt 5.15.1 jonasschnelli: Tested ACK 86b1ab6 Tree-SHA512: 1dbba8ee70c895bf58317172a9901cdbe5503b1d6258f51caaae88d88d332d9fbd4697c995192d31e3618ddfd532c5f5881289b3af1184422e5a9263a1224115
PastaPastaPasta
pushed a commit
to knst/dash
that referenced
this issue
Nov 7, 2023
…cale{Short,Long}Date 86b1ab6 refactor: Replace deprecated Qt::SystemLocale{Short,Long}Date (Hennadii Stepanov) Pull request description: As all deprecated warning in Qt 5.15.0 were eliminated in dashpay#46, Qt 5.15.1 introduced another one that is fixed in this PR. Required for bitcoin#20182. Details in Qt docs: - https://doc.qt.io/qt-5/qdatetime.html#toString-1 - https://doc.qt.io/qt-5/qdate.html#toString-1 ACKs for top commit: jarolrod: Tested ACK 86b1ab6 on MacOS 10.15.7 and Arch Linux both with Qt 5.15.1 jonasschnelli: Tested ACK 86b1ab6 Tree-SHA512: 1dbba8ee70c895bf58317172a9901cdbe5503b1d6258f51caaae88d88d332d9fbd4697c995192d31e3618ddfd532c5f5881289b3af1184422e5a9263a1224115
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there, AUR packager for "darkcoin" reporting in 😉
As of today, I update the AUR package for every 0.10.15.x release, as soon as I see them. This means by that time I check my RSS feeds, a few version numbers get skipped (was v0.10.15.3 just before, now I pushed v0.10.15.6). Sadly, Github is mixing tags and releases for
enforcement
andmaster
branches, so filtering out by branch isn't quite easy. And all tags get a release.The website isn't very helpful, as it's lagging on the
master
releases (shows v10.14.1 on a post 2 days ago, when v10.14.2 has been tagged+released 4 days ago).What do you recommend for the time being ? Following every
enforcement
release on Github or rather sticking tomaster
-only releases as announced on the website ?The text was updated successfully, but these errors were encountered: