Suggestion for a fourth alternative, do the release, but split off the 3rd
party apps with regressions out of rosapps to roswork or some such, possibly as
a separate repository, so the kernel and core apps can be focused on. Someone
fixes the regressions and that app can be moved back into the m
I vote for:1. the immediate release of version 0.4.14 as it is, with the publication of the list of known regressions in the release notes2. immediate start of preparation of release 0.4.15 just right after the release of 0.4.14 Skipping the release is not a good option as we losing PR occasion.Re
