Forum > Lazarus
We are planning the next release: Lazarus 2.0.12
Al-Eid:
Thank you and good luck
ASerge:
--- Quote from: Martin_fr on February 11, 2021, 05:42:48 pm ---- Any bug-fixes already made to trunk, that you believe should still be
merged to the fixes branch (fixes that are not listed on the above wiki page)
- Any regressions that happened in fixes branch since the release of 2.0
- Other urgent (e.g. crashes/data-loss/...) matters, you believe we should know before the release.
--- End quote ---
In my opinion, everything that has already been fixed (even the little things) should be included. There will be no other time for this anyway.
Martin_fr:
--- Quote from: ASerge on February 16, 2021, 04:08:47 pm ---
--- Quote from: Martin_fr on February 11, 2021, 05:42:48 pm ---- Any bug-fixes already made to trunk, that you believe should still be
merged to the fixes branch (fixes that are not listed on the above wiki page)
- Any regressions that happened in fixes branch since the release of 2.0
- Other urgent (e.g. crashes/data-loss/...) matters, you believe we should know before the release.
--- End quote ---
In my opinion, everything that has already been fixed (even the little things) should be included. There will be no other time for this anyway.
--- End quote ---
In principal yes. Practical there are limits. Some fixes make massive changes and/or may relay on code of new features. Merging it may carry a high risk of breaking code, rewriting it may be a lot of work. Also some fixes may carry a risk of breaking other stuff, then they may not be merged, or only be merged if they had been tested long enough.
The "that you believe" is not about whether a fix should be merged, but rather whether anyone believes a fix has not yet been merged. (Of course that includes, any fix of which someone knows for sure that it wasn't yet merged).
In that sense, any un-merged bug-fix can be brought forward. It will then - time allowing - be evaluated for merging. (Time allowing: That is the committer for each revision needs to be looked up, contacted, and they needs to decide).
ASerge:
But then the work of the team members is wasted.
The bug or feature is patched and marked as fixed. In this case, some time was spent on its preparation and verification.
But it never gets released! It doesn't really encourage others to write any patches.
JuhaManninen:
--- Quote from: ASerge on February 16, 2021, 05:04:10 pm ---But then the work of the team members is wasted.
The bug or feature is patched and marked as fixed. In this case, some time was spent on its preparation and verification.
But it never gets released! It doesn't really encourage others to write any patches.
--- End quote ---
Of course it will be released in the next major version 2.2.
Navigation
[0] Message Index
[#] Next page
[*] Previous page