On 21.12.2024 16:27, Gilbert Barmwater wrote:
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.
The question is who is going to do these updates? Are you able and/or willing
by any chance?
Or, are there any other persons (no matter whether already formally developers or not) who would be
able and/or willing to help out? If so, please come forward!
As this is an open-source project with volunteers who have different jobs, commitments it is
sometimes difficult to co-locate the resources time-wise to become able to actively co-operate for
the benefit of the project (and of its users, i.e. programmers using ooRexx)!
An important step like creating a release usually serves as a focal point to
get all open ends to meet.
So let us try to address these different open issues together in a constructive and co-operative
manner as soon as possible!
---rony
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
