They intend to work on this case during the 2023r3 cycle. That does not mean it will be completed during the cycle.
That makes senses.
The next logical questions would be
- âHow Many/What percentage of âintendedâ typically get into a release?â
Surely there is a wild guess at how long a bug will take and Xojo know how many developers it has and how many
- How are these prioritized?
Some bugs yes, some no. In the case of the item you reported above, it requires someone who has extensive knowledge of the IDE, the project structure system and has had experience working in the navigator.
My suspicion is that this is a bug that has high priority because it has high visibility, which makes it something that they want to fix, but the cost of doing so (in time and energy) is so high that it is either:
- Getting bumped for other high visibility, low cost items
- Too complex to fix without breaking other things
- Waiting for other fixes which are also getting bumped
Thanks for that insight Greg. But I still do not understand:
- How Many/What percentage of âintendedâ typically get into a release?â
- How are these prioritized?
Look on the milestone when it comes close to the release.
You can see the information.
itâs like 200 cases get a milestone assigned and maybe 20 donât make it for some reason (not visible).
See my note above about transparency. Personally I donât think itâs anyoneâs business but Xojoâs.