Maintaining last version while working on newer update.

[Kirshi912]

I'm not sure how to phrase it, let say that currently we have 115 chromium based cromite and was about to jump at 116.
May i ask if you can give 115 some breath (bug fix update) while working on 116. When 117 come out, you may abandon 115, and take care of 116.
I don't know much about software development but, let say that there is major update. New feature along with dubious patch (from your perspective) added and need to replace or re-patched (for security/privacy). Somehow, it causes problem which didn't occur before in unexpected place (i can't give an example). Whenever this browser was about to be stable (atleast closer), major update come and that cycle repeat.

I feel like this browser if it has a label, it would be 'Eternal Beta release'.
Tell me if i wrong,

[Universalizer]

https://github.com/uazo/bromite-buildtools, as Testing 'Build Alpha or Beta', if everything functions then,

https://github.com/uazo/cromite, as 'Stable build',

Idea ? Somewhat !

[uazo]

I feel like this browser if it has a label, it would be 'Eternal Beta release'.

i don't currently have an answer, google's tight schedule on chrome dictates a release every month.

May i ask if you can give 115 some breath (bug fix update) while working on 116. When 117 come out, you may abandon 115, and take care of 116.

since chrome's code is gigantic, it is not possible to make a selection on what to include and what not, assuming to keep a stable 115 (as you say) updated at least with security patches.
in fact, in the passage of each major, the implementations on security bugs are reported but the code is kept hidden, so not even simple backporting is possible. it would be necessary to look for them, read the code (and understand it, and it is not always simple) then apply it on what you call stable.

That is, impossible.