@abdullah are there any blockers beside the ones mentioned in the OP that you can think of that would block 0.19 ?abdullah wrote: pinged by pinger macro
Bugs/Issues Blocking v0.19 Release (+ WB/Addon devs check-in about Roadmap for 0.19 release)
Forum rules
Be nice to others! Read the FreeCAD code of conduct!
Be nice to others! Read the FreeCAD code of conduct!
Re: Bugs/Issues Blocking v0.19 Release (+ WB/Addon devs check-in about Roadmap for 0.19 release)
Alone you go faster. Together we go farther
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Re: Bugs/Issues Blocking v0.19 Release (+ WB/Addon devs check-in about Roadmap for 0.19 release)
I do not think so. I work with the roadmap system of the bugtracker.
I think we need to have a tentative release date (because we overshoot the one we had for 2019-12-31, I am sure for good reasons, and never updated it with a new one). This should allow to have a better idea of when the 0.20 development cycle should start. This I think is important because generally we tend to introduce "new things that may not be as stable as we think they are" or that "because of the size of the merge may require more bug fixing than usual" at the beginning of a new development cycle. But for that, we need to have an idea when the development cycle might start.
As for Sketcher tickets, most of the remaining issues are features that can be moved to 0.20 at any time. I can "triage" the bug tracker and push tickets to 0.20. At the end, it does not matter if we implement tickets of 0.20 in 0.19 and this should enable us to easily filter and identify what is really important and should be tackled better sooner than later.
In fact, I am going to do this now for Sketcher...
Re: Bugs/Issues Blocking v0.19 Release (+ WB/Addon devs check-in about Roadmap for 0.19 release)
Ok. Let's switch on the machinery.
The sketcher and GCS roadmaps are now empty for 0.19:
https://tracker.freecadweb.org/roadmap_page.php
If there is something that is really stopping release for Sketcher and GCS, reply to this post so that we set that ticket back to 0.19.
I have updated the release date of 0.19 to 31 December 2020. So we have now a tentative release date.
I suggest we bump to 0.20 the tickets of other WBs that are not going to be handled in 0.19.
Re: Bugs/Issues Blocking v0.19 Release (+ WB/Addon devs check-in about Roadmap for 0.19 release)
I submitted a PR for this one: https://github.com/FreeCAD/FreeCAD/pull/4036Kunda1 wrote: ↑Sat Oct 10, 2020 12:02 pm Release Blocking Bugs
- issue #4453: Error triggered when trying to clear the property by the property editor and Link dialog
Re: Bugs/Issues Blocking v0.19 Release (+ WB/Addon devs check-in about Roadmap for 0.19 release)
I suspect that this one was fixed in PR 3954 by marioalexis84, but I can't get Draft to run on my current machine, so I am unable to test.Kunda1 wrote: ↑Sat Oct 10, 2020 12:02 pm Release Blocking Bugs
- issue #4416: "Cannot normalize null vector" in Draft2Sketch
Re: Bugs/Issues Blocking v0.19 Release (+ WB/Addon devs check-in about Roadmap for 0.19 release)
I retested 4416: it is solved and I closed the ticket.
A Sketcher Lecture with in-depth information is available in English, auf Deutsch, en français, en español.
Re: Bugs/Issues Blocking v0.19 Release (+ WB/Addon devs check-in about Roadmap for 0.19 release)
Associated issue #4416 with the appropriate commit within the tracker ticket. Thanks to all for working on this!
Alone you go faster. Together we go farther
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Re: Bugs/Issues Blocking v0.19 Release (+ WB/Addon devs check-in about Roadmap for 0.19 release)
Just tested this using OCCT 7.5.0 and it doesn't segfault, so this may have already been fixed upstream. The output I get is:Kunda1 wrote: ↑Sat Oct 10, 2020 12:02 pm Release Blocking Bugs
- issue #4247: GeometryCurvePy::intersect / GeometryCurvePy::intersectCC Segmentation Fault with OCC 7.4
Code: Select all
>>> e1.Curve.intersectCC(e2.Curve)
Traceback (most recent call last):
File "<input>", line 1, in <module>
RuntimeError: NCollection_Sequence::Value
Re: Bugs/Issues Blocking v0.19 Release (+ WB/Addon devs check-in about Roadmap for 0.19 release)
This is marked fixed in Mantis, and I retested today and it seems to be working properly.Kunda1 wrote: ↑Sat Oct 10, 2020 12:02 pm Release Blocking Bugs
- issue #4456: Regression : Part.Plane.Intersect do not accept plane as argument
Re: Bugs/Issues Blocking v0.19 Release (+ WB/Addon devs check-in about Roadmap for 0.19 release)
Thanks! I've crossed it off in the OP.
Alone you go faster. Together we go farther
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs