On 15/01/06, Karoly Negyesi <karoly@negyesi.net> wrote:
First of all, it is not late. It'll be out when it's done and noone said it otherwise.
I might be speaking out of turn here, but I totally agree with this sentiment. However, when is done done? For any software project, regardless of how simple or complex it is, or what model it follows, there will _always_ be bugs. So, it's something of a catch-22 that the longer the delay, the more bugs are found and the longer the delay and .. There needs to be a line drawn somewhere.. I realise you've linked to a couple of issues on here, but I'm sure there are more. Is there a list of issues, that if solved will lead to a 4.7 release? If not, shouldn't there be one? I've also read on the forum that the bug-fixing parties concentrate on all outstanding bugs and patches, regardless of whether they are to be included in 4.7. So, as someone has already attempted to organise, there should be a Priority level named "Hyper-critical" or something similar, that can only be set/unset by the primary core developers. This should allow better control of the project's workflow and enable everybody to concentrate on getting 4.7 out the door. Or in the meantime, a list of such issues could be posted, publicised and regularly updated somewhere.. Anyways, I'd love to help if/where I am able to, but only if I know what to help with exactly. IMO, we just need to tackle this in a systematic manner. Thanks for listening :) Regards, Karthik.