September 2016 - Neon.1 - CDT 9.1 (from the master branch)
December 2016 - Neon.2 - CDT 9.2 (from the master branch which then becomes open for Oxygen development)
March 2017 - Neon.3 - CDT 9.2.1 (from the cdt_9_2 maintenance branch)
June 2017 - Oxygen - CDT 9.3 (from the master branch)
Concerns about "automatic and continuous maintenance release"
Strong hesitation about making builds available that won't be kept available in the future.
Some ideas:
Don't enable such a maintenance update site by default. This will allow those that want it to make a conscious choice. Problem is that most users won't even know they can choose to get latest bug fixes like that.
Don't provide "automatic" releases but instead provide "manual" ones on demand. There will be less such releases and we will be able to keep them. Problem is that this requires someone requesting such a release, even though we know something has been fixed and could go to users.
Do the "automatic" releases but retain them all. Could be too many builds.
Do the "automatic" releases but at a lesser frequency, maybe once a month + "manual" releases upon request.
This discussion will continue at the next CDT call
Recommendation is to focus on problem at hand (deleting source folder) and workaround the issue. It would probably not be worth investing if fixing the root of the problem unless really necessary, as it could cause many other problems.