Could we write down a roadmap of needed operations until FLTK 1.4can be presented as a Release Candidate?
I believe that branch contains important new features (HiDPI support,CMake-based building, Pango support for the X11 platform) that would
be useful for many FLTK users.
A roadmap would help to reach that goal.
+1
Usually this involves just going through all the bugs and
listing the items that
must be fixed for release, and lower the priority of items
that can be delayed for
subsequent maintenance releases.
As Linus always said, "release early, and release often."
Doesn't seem to be our motto, but maybe should, lol.
Since this is a major release (1.4.0), we should put some
priority on anything that
affects ABI, esp. if it involves adding members to structures
that can be used in
later fixes. Sometimes thinking ahead like adding a char just
for bit flags we know
we'll need can be useful to prevent ABI breakage during the
maintenance path.
One issue that clearly needs fixing is #93It contains a proposal for a work-around, but another approach may also be considered.
I might be wrong, but pango support could probably be moved
to being a fix in
a maintenance release, esp. if it's a tough one to solve.
As I think Albrecht mentioned somewhere, perhaps in an issue, there needs to
be a search for FIXME and maybe XXX/TODO items.