You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: