Hey,
Why do you want it to be in the core? I thought it was designed as an
extension.
No, the idea is to have all deployment code in core in the end. It doesn't make much sense to have to manually go install an extension in order to do it automatically. The reason for the code currently being in the Deployment extension is that this allowed me to do more experimental things with it, and finish it up nicely before having it in core. If you look at the class names you can see I never intended this as extension by the lack of prefixes.
Would a new installer not be unusable as an extension.
The new installer is already in core. This thread is about the non-core-installer deployment code, such as detecting extension updates, browsing through extensions that can be installed, getting them and installing them.
Cheers Jeroen De Dauw