Skip to content

3.10 #1

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

Open
wants to merge 277 commits into
base: master
Choose a base branch
from
Open

3.10 #1

wants to merge 277 commits into from

Conversation

jcampan
Copy link

@jcampan jcampan commented Mar 14, 2017

No description provided.

tianon and others added 30 commits April 28, 2016 10:21
Add a hacky workaround for CASSANDRA-11661
The only releases listed as supported on https://cassandra.apache.org/download/ are 2.0, 2.1, 3.0, and 3.5.

Additionally:

> Even-numbered releases (e.g. 3.2) contain new features; odd-numbered releases (e.g. 3.3) contain bug fixes only. If a critical bug is found, a patch will be released against the most recent bug fix release.

Also: (http://www.planetcassandra.org/blog/cassandra-2-2-3-0-and-beyond/)

> Under normal conditions, we will NOT release 3.x.y stability releases for x > 0.  That is, we will have a traditional 3.0.y stability series, but the odd-numbered bugfix-only releases will fill that role for the tick-tock series — recognizing that occasionally we will need to be flexible enough to release an emergency fix in the case of a critical bug or security vulnerability.
Remove 3.1, 3.2, 3.3, and 3.4
More aggressive on setting seeds value
added jemalloc shared library
> Note: Instead of using this command a keyring should be placed
> directly in the /etc/apt/trusted.gpg.d/ directory with a
> descriptive name and either "gpg" or "asc" as file extension.

https://manpages.debian.org/cgi-bin/man.cgi?query=apt-key&manpath=Debian+testing+stretch
Use "/etc/apt/trusted.gpg.d" instead of "apt-key adv"
docker-library-bot and others added 30 commits May 20, 2024 13:24
(this is effectively a functional no-op solving a "problem" that really ought to be solved at a different level within GHA)
Attempts to upgrade 3.x versions to Ubuntu Noble fail because they still require python2 (which is no longer available in Noble).

Attempts to upgrade 4.x fail because of incompatibilities with Python 3.12 (which is the version Noble has).

Attempts to upgrade 5.x fail because of the above Python 3.12 incompatibility, but with the added benefit of code detecting that we're trying to use Python 3.12 and erroring that no suitable Python version could be found (instead of failing with an obscure `six.moves` import error, like 4.x does).

For now, this is an explicit override for every supported version because hope springs eternal that Python 3.12 will be supported eventually and some future 5.x will be able to upgrade to Ubuntu Noble. 🙈
Lock all versions to "jammy" (no "noble" auto-upgrade)
This makes it print out a diff when there is an error (instead of just a list of files that are wrong), which will make the error more obvious.  I also added `workflow_dispatch` so we can run it manually.
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

Successfully merging this pull request may close these issues.

10 participants