On Fri, 11 Dec 2009 07:08:32 +0100 Ulrich Mueller wrote: > > * Don't commit the EAPI 3 / 4 changes until the Council are done > > changing things, > > From the summary of the December Council meeting [1]: > > | EAPI-3 status > | ============= > | [...] > | Because prefix support will be EAPI-3 (see below), the EAPI items > | referenced here will be referred to as EAPI-4 in the future. > > Official Council decision, therefore nothing to discuss. (And no, we > won't rename it back.) Sure. But we don't have a spec of what EAPI 3 is, so we can't do anything with it. We also don't know when we'll have a spec of what EAPI 3 is, so there's no point in tinkering with PMS until we do. We've tried to avoid having huge chunks of "todo" on the main branch since we started viewing PMS as being more or less correct, and adding them back in again is a huge step backwards. We did all the original EAPI 3 work on a branch and didn't merge it until it was done for a very good reason. > > We also don't have approved summaries of any of the meetings where > > these things happened. > > And what is [1] then? Something that wasn't there when I sent the original email, as you know very well. -- Ciaran McCreesh