Wedge

Uh i couldnt see anythin more on this so im bumping about the pages, all SMF stuff have been moved to a new folder pretty much:

http://www.simplemachines.org/about/smf

so the team page is now at:

http://www.simplemachines.org/about/smf/team.php

The about page does have a link to SMF (appropriatley linked as SMF) and is now about Simple Machines aka the NPO  ... just wanted to clear that up a wee bit :P

Anyway 2 days to got and I see 5 unresolved bugs ... getting close it is

Yes, we noticed, probably multiple pages ago. We noticed a great number of things like the inconsistencies in the now-two menus some of which seem to have been resolved by now, not to mention the fact that while there are 5 unresolved bugs, how many more were merely deferred to 2.1 instead of being solved for 2.0?

see im too tired so i appologise for missin those things ... as for the bugs no idea i can barley use the bugtracker (it sucks)

No need to apologise :) It's not exactly the most obvious thing to spot. And yes, Mantis sucks. I found myself installing it to see how it did something with its permissions, and I found myself hating it even more when using it locally :/

5? What am I doing wrong then as I can see 19 with this link:
http://dev.simplemachines.org/…ht_changed=0&hide_status_id=-2

I see 21...

Bloody hell, this is confusing :(


Presumably we'll know it's about to be released when they all get shifted over to 2.1 and the 2.0 bugs outstanding goes to 0.

Not really, the 2 I see that you don't are marked as private in the tracker.

They are all minor things, not a *real* security issue? That's a good reason to release SMF as final...

The outstanding 20 or so are minor.

The ones already pushed back, some of which are YEARS old, mostly minor too. My beef with what they're doing is less about what they decide to fix and what they decide to defer (it IS about that, but not so much).

My main beef is how we had all this BS for months about how 2.0 final was going to be bug free, with no issues left in the tracker. Sure, if you just sweep them under the carpet!

If they were prepared to man up and admit that there are issues outstanding that they're going to fix and not this 'final/bug free' BS, I'd give them some lee-way, especially since none of the deferred bugs are going to be fixed in 2.0.1 as and when it emerges, since 2.0.1 will be security or major-earth-shattering issues.

Considering that some of the bugs are minor and have documented fixes that don't break anything and certainly don't cause any regression errors (there's FUD before you start!), it's fairly poor to just defer them when you could fix them and retain some of the element of integrity about what you do.

Personally, I just think it looks bad, especially given how long it's been in RC status.

...And that's even without mentioning that RC is supposed to be "ready for release, just making sure there aren't any breakers on a larger scale" ;)

Haha, try THAt with SM and get mangled butter in return :P

They simply should have remained in Beta longer... And stopped treating their teamies like shit and causing them to leave and abandon their ongoing work... ::) (e.g. January split.)

I can elaborate on that a bit actually.

RC1 wasn't really ready to be an RC, it didn't even have Curve in it. The only reason it wasn't 2.0 beta 5 was because they promised the next version would be RC.

RC2 was the first real RC and that had some major flaws in it too. I don't remember how many people were still considering that as a beta too.

RC3 was the first time that the software could genuinely be called an RC, but even that far back some of the more minor bugs were starting to be deferred rather than fixed.