Prepare releases and packaging
See original GitHub issueTo bring this project further we can start tagging releases which also potentially will make it packable for distributions. With #57 we have a solid base for future changes we can build upon.
-
Script adjustments
- Care about repo installations (#77)
- We should re-evaluate our self-update part since it will probably much more frequent be a plain download or repo installation instead of a git checkout. We should also consider a way to disable this check, maybe on path detection? (#82)
- Automate update branch detection (#63)
- Sane defaults for everything (#69)
- Proton as default
- Start as default
- Update as default?
- ETS2 as default
- Automatic current steam user detection. (#67)
- Remove waiting on user input in
start_with_wine()
(#83) - I probably missed something…
-
Github adjustments
- We should create a new GitHub action which will create a changelog since the last release and bundle everything up in case someone finds the release section. (#64)
- Start tagging releases (#78)
- Remove the binary from the repo and include it in the release tarball (#78)
- Update README (#80)
- Dependencies > Optional (Add (python3-)pip and vdf)
- Install (Replace current content with new installation instruction after publishing)
- Overhaul everything as it’s quite messy
- Add us to it
- Investigate automatic bash/zsh autocompletion generation (#70, #75)
- provide installation through
setup.py
(#77) - try to package for PyPi (#81)
- Care about PyPi installations (#80, #81)
- Provide an Issue template (#74)
- Code blocks and spoiler for logs
- I probably missed something…
Issue Analytics
- State:
- Created 3 years ago
- Comments:10
Top Results From Across the Web
Chapter 7. Packaging, Releasing, and Daily Development
This chapter is about how free software projects package and release their software, and how overall development patterns organize around those goals.
Read more >Chapter 7. Packaging, Releasing, and Daily Development
This chapter is about how free software projects package and release their software, and how overall development patterns organize around those goals.
Read more >7. Releasing your package
In preparation for your package's initial and each subsequent release, ... Update the version number to that of the release you are going...
Read more >Release Packaging and Build Manager
The Release Packaging and Build Manager user role has the following responsibilities: Change Analyst who transfers the new release from development to test ......
Read more >The Essential Guide to Release Management | Smartsheet
In this guide to software release management, learn how to plan, build, test, and deploy new releases, and find free templates.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Whoops, I seem to have accidentally already checked the box for waiting on user input in
start_with_wine()
which isn’t resolved yet. Discussion was in #63 Good thing I’ve rechecked everything…No problem, would be fine 😉
What bothers me about
-c
is that’s only a one-time command. And the actual DX11 argument only exists in a long version. I’ll propose to remove-c
and add-d
for--enable-d3d11
.-b
is also a good addition.That’s what I meant with syncing the help texts.