That's precisely my point. I could forgive this delay if there were any real evidence of any changes. The tracker doesn't agree, and the only line that the team are giving is that there are bugs being fixed.
I sync'd Wedge's SVN to SMF's on 21st May, that was rev 10542. They're now on rev 10560. I see at least two revs not related to 2.0 in those 18, I see a few credits updates, but I'm not really seeing anything that's setting my world on fire with bugfixes - I see more template bug fixes than other bug fixes in fact, hardly anything that would - in my mind - justify their delay, when the tone of some of the team members who are toeing the party line is that there was something big enough.
See, here's where I have a problem. On the one hand, they're not going to fix a number of minor bugs, but they're going to fix other minor bugs, that are equally aesthetic and minor as the ones they've actively said they're not going to fix this time around. On the other hand, they're saying about how there's something that required them to delay it to get it fixed, but no-one's saying what, and it's not like SVN indicates anything, so unless there's a security hole or major show-stopping bug that isn't documented anywhere outside the team area, I can't call it as anything other than 'shit, we called a deadline and now we failed on that again'.
I sync'd Wedge's SVN to SMF's on 21st May, that was rev 10542. They're now on rev 10560. I see at least two revs not related to 2.0 in those 18, I see a few credits updates, but I'm not really seeing anything that's setting my world on fire with bugfixes - I see more template bug fixes than other bug fixes in fact, hardly anything that would - in my mind - justify their delay, when the tone of some of the team members who are toeing the party line is that there was something big enough.
See, here's where I have a problem. On the one hand, they're not going to fix a number of minor bugs, but they're going to fix other minor bugs, that are equally aesthetic and minor as the ones they've actively said they're not going to fix this time around. On the other hand, they're saying about how there's something that required them to delay it to get it fixed, but no-one's saying what, and it's not like SVN indicates anything, so unless there's a security hole or major show-stopping bug that isn't documented anywhere outside the team area, I can't call it as anything other than 'shit, we called a deadline and now we failed on that again'.