| |
| |
On 11/23/20 9:40 PM Greg Ercolano wrote:
On 2020-11-23 12:08, Evan Laforge wrote:
Since this is a major release (1.4.0), we should put some priority on anything that
affects ABI [..]
There are also a bunch of non-virtual methods that could be made virtual [..]
+1 -- now is definitely the time to do that sort of thing.
Yes, I had a lot of such non-virtual methods in mind as well, but some
of these can't be easily converted to virtual. Unfortunately there are
too many conflicts. I can investigate (and look in my internal notes)
for more info tomorrow.
As I think Albrecht mentioned somewhere, perhaps in an issue, there needs to
be a search for FIXME and maybe XXX/TODO items.
That sort of thing is what I'd like to get done before we release 1.4.0.
Technically spoken: GitHub has a "Milestone" feature we could and IMHO
*should* explore for this goal.
I created a Milestone "1.4.0" to try that feature some time ago. We can
add issues as we like and should try to resolve those (first) before we
release 1.4.0. Of course we need to find consensus about what issues
(and STR's) should be resolved in 1.4.0.
Note that I added two "random" issues, this needs to be checked and
evaluated. We can of course remove these (or not).
https://github.com/fltk/fltk/milestone/1
(go to https://github.com/fltk/fltk/issues and click on "Milestones" to
go there).
I'll add more of my thoughts and open issues tomorrow or even later...
--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/ab491ec3-dfa2-4860-43d3-7d117a301c1d%40online.de.
[ Direct Link to Message ] | |
|
| |
