What do you plan for the XLibre Upgrade and Deployment Cycle? #96
-
I was curious what your plan was for the continued development and release cycle for X11Libre. Any distribution wishing to move to X11Libre will want to have a stable version. Otherwise, they can only have it in their unstable repository. Do you plan on making a cut off point for changes sometime soon so that version can be tested enough to be considered stable? Meanwhile, continue developing it in another version? Do you plan on making a significant number of changes first that will take awhile before you cut off changes at some point so that version can be tested for stability? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
Thank you very much for your question! I'm sorry it only came to my attention lately.
Yes, that is clearly understood and there is already a X11Libre/xserver at maint-25.0 branch for stabilizing the 25.0.x version of XLibre. Once this is done we will release a 25.0.1 version and further 25.0.x versions from that branch/feature set for bug fixes only. New features will be developed on the master branch, very likely using feature branches as the GitHub flow - GitHub Docs implies. So the development will be isolated from the release branch(es). One of the next steps will be to concretize and formulate our branching strategy and refine it in the course of ongoing development. @Ryu945 Does this answer your question? |
Beta Was this translation helpful? Give feedback.
-
As a sidenote: We are about to consolidate our support for packaging XLibre. Please see Consolidate support for packaging XLibre by our community · X11Libre · Discussion #101 for more. |
Beta Was this translation helpful? Give feedback.
Thank you very much for your question! I'm sorry it only came to my attention lately.
Yes, that is clearly understood and there is already a X11Libre/xserver at maint-25.0 branch for stabilizing the 25.0.x version of XLibre. Once this is done we will release a 25.0.1 version and further 25.0.x versions from that branch/feature set for bug fixes only.
New features will be developed on the master branch, very likely using feature branches as the GitHub flow - GitHub Docs implies. So the development will be isolated from the release branch(es).
One of the next steps will be to concretize and formulate our bran…