On Mon, Aug 16, 2010 at 4:57 AM, Tim Starling <[email protected]> wrote: > On 16/08/10 18:41, Jeroen De Dauw wrote: >> 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. > > I think you should leave it as an extension for now, until it is > completed and reviewed. We can worry about core directory structures > if and when it's accepted. > > If it is merged in, we'll probably be aiming for release in 1.18, > which means it will have to stay either in an extension or a branch > until the 1.18 branch point. > > -- Tim Starling >
+1. I've tried to make it very clear that 1.17 needs to be feature complete sooner rather than later; I'm definitely enforcing this in the installer. I think this is great stuff, but best targeted for post-branching like Tim said. -Chad _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
