Skip to content
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

Safe updates #7

Closed
dilyn-corner opened this issue Oct 12, 2020 · 0 comments
Closed

Safe updates #7

dilyn-corner opened this issue Oct 12, 2020 · 0 comments

Comments

@dilyn-corner
Copy link
Owner

One of the major goals I have is pushing nonbreaking updates. Essentially, this means that all 'large' version bumps (plasma/frameworks) will be done as PRs. This might 'slow down' updates, but the initiated user will simply be able to checkout the relevant version branch for updates. These branches shouldn't be long-lived - they will mostly exist to stage pushes while we wait for upstream to publish the tarballs (code changes are rare close to version bumps, but they like to stick to a schedule).

Additionally, this will mean not completely breaking package installation. I doubt anyone noticed, but recently hacks were done to polkit that would cause catastrophic failures if it had been done the way I did it for any popular distribution - namely, renaming the package and breaking it entirely. I don't think this repository is well-used, but I would prefer to utilize Github's features if we're distributing our packages that way in the first place. As a result, there will be branches from time to time for various experiments and tweaks. Use those branches at your own risk.

Ideally, the main branch will remain fully-functional and nonbroken at all times.

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

No branches or pull requests

1 participant