Well, another year has gone by since this was last proposed and to my
knowledge, we still have NOT addressed the "unfinished business" left
over from the 5.0.0 release, namely the bug fixes and RFEs that were
never officially closed. From my post of 29 Nov 2023:
"I guess I need to refresh everyone's memory on this topic. When we
released 5.0.0 about a year ago, it contained a lot of changes! The
CHANGES file listed 361 bug fixes, 169 RFEs, 66 documentation bug fixes
and 10 patches. Unfortunately, some of the bug fixes and RFEs were NOT
in the "pending" state but still in the "accepted" state which indicated
additional work items - typically doc, and/or test - were not complete.
Rather than delay the release any longer(!) until they were all in the
pending" state", it was decided to proceed, listing them as included in
the release. Shortly following the release, all the "pending" items
were changed to "closed" as well as SOME of the "accepted" ones. Since
that time, additional items have been completed and their status changed
to "pending" or "closed" but there remain a number that are still
unresolved. My analysis indicates that there are 11 bugs - 1447, 1624,
1625, 1656, 1742, 1762, 1763, 1786, 1827, 1837, and 1838 - and 11 RFEs
- 353, 544, 550, 552, 569, 576, 578, 581, 603, 754, and 803 - still to
be completed. Whether we decide to do a bug-fix release - 5.0.1 - or a
new feature release - 5.1.0 - it is time to clean up this "unfinished
business".
Perhaps some of these have been resolved since then but I suspect that
most of them haven't been since they are "out of sight, out of mind".
In any case, it is easy to check each of them to get a "current" list of
what remains to be addressed.
To me, ignoring this issue is simply unprofessional and "sloppy" and we
ought to clean it up or we risk setting a precedent that this project is
not serious. Just my opinion.
Gil B.
RexxDay 16,714
On 12/21/2024 4:25 AM, Rony G. Flatscher wrote:
Is there anything that needs to be done before creating a new release
of ooRexx 5.1.0?
When would who be available in the next ten to fourteen days to start
the process by creating a release candidate?
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
--
Gil Barmwater
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
