distribution icon indicating copy to clipboard operation
distribution copied to clipboard

About the mirror update release issue

Open GithubServers opened this issue 1 year ago • 9 comments

The Clearlinux image distribution should be updated by packages, not by releases like this once every few days. This can be very frustrating and even difficult for users to adapt to new issues, and it's time to rethink this issue

GithubServers avatar Mar 20 '23 08:03 GithubServers

Can you expand on what you think the problem is? Is it that we need to release faster? We'd be QAing the content together and push the content at the same time, so regardless of how we push, the content will be somewhat "atomic" ...

fenrus75 avatar Mar 20 '23 14:03 fenrus75

I think Clearlinux should be divided into base and package updates. Base component updates necessary for the system should be the primary vehicle for building new images, and package updates should not be integrated into new image builds but should be more of a command to get the updates you need. The "out-of-the-box" philosophy has caused more problems with updates in the past history of mirrors.

GithubServers avatar Mar 21 '23 00:03 GithubServers

Updates to packages should be carefully reviewed and tested prior to release so that they can be better oriented across a portfolio of different users.

GithubServers avatar Mar 21 '23 00:03 GithubServers

we review and test all updates of course

but I still don't get what problem you are solving. now it sounds like you don't want updates as fast ?

On Mon, Mar 20, 2023 at 5:30 PM GithubServers @.***> wrote:

Updates to packages should be carefully reviewed and tested prior to release so that they can be better oriented across a portfolio of different users.

— Reply to this email directly, view it on GitHub https://github.com/clearlinux/distribution/issues/2855#issuecomment-1477127504, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJ54FOUZZZYHCLQTJNAIS3W5DZCDANCNFSM6AAAAAAWAYM2K4 . You are receiving this because you commented.Message ID: @.***>

fenrus75 avatar Mar 21 '23 13:03 fenrus75

I mean the package should be updated faster, but will the updates via upgrades be subtly different from the newly released images?

GithubServers avatar Mar 21 '23 14:03 GithubServers

hmm I still don't understand.

images are for installing, and at that point they get instantly updated to the latest online version ?

On Tue, Mar 21, 2023 at 7:50 AM GithubServers @.***> wrote:

I mean the package should be updated faster, but will the updates via upgrades be subtly different from the newly released images?

— Reply to this email directly, view it on GitHub https://github.com/clearlinux/distribution/issues/2855#issuecomment-1477977774, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJ54FMNYMVDEGFBB36TD4TW5G5ZXANCNFSM6AAAAAAWAYM2K4 . You are receiving this because you commented.Message ID: @.***>

fenrus75 avatar Mar 21 '23 14:03 fenrus75

Has it become more bloated after upgrading from the historical version image to the latest version update package? Will it be updated and upgraded like the latest release of the image installation?

GithubServers avatar Mar 21 '23 15:03 GithubServers

<so regardless of how we push, the content will be somewhat "atomic"> Packages of non-system components should be divided into component pools, and only the base and necessary component packages should be updated for each release of the image.

GithubServers avatar Mar 21 '23 15:03 GithubServers

Clearlinux are rolling release distro but with version per each update. having update per package can't be done as clearlinux uses bundle when lot of packages combined. correct me if i'm wrong

NextGenOP avatar Sep 14 '23 23:09 NextGenOP