There is a release process:
https://www.fltk.org/cmp.php#RELEASE
In
the old CMP,
the requirement was to absolutely solve all High and Critical bugs
before release. All moderate/low/RFEs that can't be solved by
release would be bumped
to the next release for resolution.
[ . . . ]
The
STR System provides some level of
bug tracking and TODO list management that comes into play
when a release nears. Between releases, it mostly acts as an
accumulator.
And we've since moved to github issues for managing bugs.
The STR's are there as a history, and to finish still-open
issues/bugs/RFEs.
There's currently 112 STRs against 1.3 (0 critical, 0 high,
25 moderate, 26 low, 61 RFE's)
There's currently 189 STRs against 1.4 (0 critical, 17 high,
22 moderate, 29 low, 121 RFE's)
In github there's 60 open issues, I don't think we have a rating
system for those, [ . . . ]
In theory, there's nothing to stop a determined "user" who is expert in a particular area
helping with the open STRs and github issues and supply patches or pull requests, but
in reality many of the 17 "high" STRs require some serious knowledge of the internals
of FLTK and/or the subtleties of working across different platforms and compilers with
specific third-party libraries, Unicode and Internationalization.
But that's why people are using FLTK: to hide those internals for cross-platform tools.
Personally, I have no desire to learn about the internals of X11, Windows or MacOSX.
So if you aren't working on these things anyway as part of your day job, there's a lot to learn!
I've looked but here really aren't many "low hanging fruit" that can be picked off the STR list :-(
