XBMC feature-freeze and bug-bash!

@tzon, from the first post in this thread!:

(gamester17 @ mar. 07 2006,10:33 Wrote:please do not post bugs, feature suggestion or help/support requests in this topic thread. read and follow the xbmc faq, thanks in advance.

at first i was thinking of asking you when you think the new mc360 skin will be released, in accordance with the stable point release. but then i realized that i would be selfish to ask, considering you guys do this for free, and do such a remarkable job. not to mention the fact that the cvs is updated every day, so we know you're working on it, and the program itself is so incredible, that its definitely worth more than free.

so i just want to say thank you for doing this, keep up the good work, and know that there are thousands of people that appreciate the work you do.

you guys rock; hardcore.

yes xbmc is a great project and i find it amazing how frustrated people are about bug bashes. its common knowledge i thought that software needs to become stable, especially if its the core of your entertaining needs.

bug bash on and create a super sweet 2.0.0 release :thumbsup:

whats the progress?

i know u guys don;t want to say anything abut the release date but can atleast give an absolute max date of release?
so i dont have to keep anticipating (its killin me)

it will be ready once it's ready. no max dates, no min dates, no dates...

(tslayer @ april 22 2006,19:53 Wrote:it will be ready once it's ready. no max dates, no min dates, no dates...

whats the status are you almost done or "oh, we haven't even started".

i looked around to see how many bugreports there were and how many were closed, but i haven't found any.

so could you please give us an inclination of what you feel is the status of the freeze 10% done 50% 99% ( )

(as no dates will lead to many many many: "are you done yet, are you done yet, are you...") but a % is more nice to the little kids of no patience.

i must note that even though the bug bash makes sense, i don't understand the no timeframe deal. obviously i respect the choice of the developers on this one because they code it but my programming experience suggests its best to set goals or else it will never get finished.

not trying to be rude here anyone just stating something that i think the developers should at least think briefly about. goal setting is a common thing in this world and while i'm patient and it would be fine if it took another year, it seems to just make more sense to have a timeframe. almost all serious projects do is what i'm trying to get across.

the reason for the no timeframe deal is just the problem that less dev's are interested in fixing bugs than adding features. and thus, you can never really tell how long its going to take.

at the moment we're doing some major changes to where xbmc saves stuff like databases & settings, this will need alot of testing

@drakethegreat, just bringing the point up is "rude" in a sense.
we do as best we can, and when we feel like announcing a timeframe, we will.

well i guess we don't see eye to eye on whats rude but that seems to make more sense. i guess people are confused as to what exactly is going on. for instance i don't understand what if any code exists for 2.0.0 and i hear stories about what features will be in it but if all the development efforts are on bug bashing (which is a good thing too) then are these features even being worked on for 2.0.0? its just confusing because everyone who doesn't have full cvs access is somewhat confused or maybe it is just me

thanks for replying though.