hi Philipp,
my reason to stick with 3.6 (for now) is clearly the source-only
distribution. I consider myself a user rather than a bug-tracking
expert. Apart from that I have never compiled such a big software. So I
figured I might just as well wait until binaries are available. But
that's just me...
Regards,
Georg
Am 20.03.2018 um 13:44 schrieb Philipp Klaus Krause:
In the past, for a few weeks after a SDCC release, there usually were
quite some bug reports coming. People migrated to the new release and
reported regressions. SDCC 3.7.0 was quite unusual in the high number of
changes since the previous release, so I would have expected lots of bug
reports.
However, this is not what happened. Actually, I didn't see any increased
activity on the bug tracker at all. I wonder why. My guesses are:
1) Few regressions. SDCC regression testing covererage gets better all
the time, so potential regression are caught early and don'T make it
into releases.
2) SDCC users are still using 3.6.0 instead of 3.7.0. If this is the
case, there is again a question of why. 3.7.0 was a source-code only
release. Did that prevent some from moving on to 3.6.0? Any other
reasons to stay with 3.6.0?
Philipp
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Sdcc-user mailing list
Sdcc-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sdcc-user
