While I understand that you're excited about new features and bug fixes you should hold your horses and wait until upstream deems their software ready (by issuing a release).

Read the open letter here: do-not-ship.it/

@devrtz so true. (as a newbie) I wonder if there are nightly builds people (not maintainers) can opt into to get these 'new features' and WIPs?
Or would that be too much of a hassle for developers of core components?

As both an upstream developer for and a package maintainer for let me share my (ideal) workflow:

- Start hacking on Feature/Bug X
- Open (WIP/Draft) MR
- Hack some more
- Once it's ready for review unWIP/undraft it
- Fix issues that crop up during review until everyone is happy
- Test drive it for a bit
- Merge

- Repeat for Feature/Bug Y
- Make release
- Update the package and upload it

· · Web · 0 · 0 · 0
Sign in to participate in the conversation

A newer server operated by the Mastodon gGmbH non-profit