Presumably quadruple reed instruments (that require even more air pressure to play) would be even better: https://en.wikipedia.org/wiki/Quadruple_reed
521 karma · joined April 26, 2016
Socials: - github.com/carwyn - http://northwales.tech/
Interests: Art, DevOps, Gaming, Mentorship, Networking, Open Source, Programming, Remote Work, Research, Startups, Technology
---
Presumably quadruple reed instruments (that require even more air pressure to play) would be even better: https://en.wikipedia.org/wiki/Quadruple_reed
https://cloud.google.com/blog/products/serverless/cloud-run-...
Nice idea, nowhere near ready for anything but playing.
Labels are repo only and multi valued. Issue types are organisation wide and single valued, project fields are the richest, but no multi-valued option, and they end up in a disjointed place in the API (you can't get at them easily when what you have is the issue, you have to go in via the project).
An example of this disjointed feeling it that there are no "issue type"s for a PR. This means that if you want to share metadata between PR and Issues, you have to use labels anyway.
I do wonder if types could have been better implemented as namespaces for labels. This combined with being able to have organisation or repo context label namespaces would have allowed for far more flexibility.
The other thing that vanished from the public roadmap amongst all this was support for better workflows. Currently there's no easy way to create allowed state transitions between metadata state (e.g in a project stop issues being able to skip the QA status).
The attention this area is getting is welcome, and there are many good things in there, but it does feel a bit disjointed. A more unified metadata model would be welcome.
The metaphor is more of containers/projects and save slots/objects. Far more like video games than the traditional model.
Fireball XL-5, Supercar, Joe 90, Space Precinct (sub needed), UFO, Terrahawks, Space:1999, The Secret Service, Stingray, Gerry Anderson's New Captain Scarlet (3D), Captain Scarlet, Thunderbirds the Anniversary Episodes, Thunderbirds Are Go (3D), Thunderbirds.
If you have a support contract though and open a case, the level and quality of support is usually very high.
Are there any games out there since that capture this as well? Most I've seen since don't seem to capture the need to work with others nearly as well, usually as all classes can do too much.
Shame, the code review was good and one of the few that supported task dependencies :(
Also excellent for ease of adoption with beginners due to zero install overhead.
https://www.theregister.com/2021/02/12/footfallcam_twitter_k...
https://cybergibbons.com/security-2/serious-issues-in-nurser...
In many respects I'd rather have a slow trickle of updates than the current flood of each point release. We've had lots of experience of dealing with all those changes landing at the same time breaking things.
As per the FAQ though I suspect there is more to this than meets the eye. Two things strike me: 1. The suggestion that low or no cost options for RHEL are coming for certain categories of user. 2. As much as Stream will be a rolling and "beta" channel, Fedora/CentOS/RHEL already have testing repos within their release process so Stream may not be as unstable as this might first suggest.
With local staged repository mirrors Steam may end up being less volatile than the existing point releases which were notorious for breaking things at times.
Rawhide <=> Sid
Fedora <=> Semi-stable-ish but short-lived and moves fast.
CentOS Stream <=> Bullseye but possibly less stable than Fedora in parts.
RHEL <=> Buster
This does really vary hugely from team to team and even project to project though. I fear "agile" methods have forgotten the meaning of the word they are based on at times. Regular re-factoring also applies to development and operational models I find.
[defaults] inventory = ./inventory/hosts
Many suggest games like Diablo but it tends to play more as a scaled single player game than a genuine balanced composition group game (i.e. if you're not hearing/feeling "Need healer/dps/tank"! it's not what I mean). MOBAs brought this for PvP but there are many out there that simply like good ol' PvE co-op with character and strategy.