Posts: 64
Joined: Apr 2005
Reputation:
0
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.
Posts: 3,805
Joined: Mar 2004
Reputation:
3
elupus
Team-XBMC Developer
Posts: 3,805
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.
Posts: 26,215
Joined: Oct 2003
Reputation:
187
the general consensus is:
no new major features for 2.0.0. ie what you see now, is pretty much what you'll get feature-wise.
with that said, there are a few outstanding things that could be considered minor features that aid to the ease of use of the software which will be in before 2.0. for instance, the rearrangement and cleaning up of the settings interface and the folder structure. another thing is the thumb tracking is getting some work as it is not obvious (both from a code perspective and a user perspective) as to what takes priority (local thumbs vs imdb thumbs vs allmusic.com thumbs etc.)
what you get in anonymous cvs is exactly what the developers have, save for anything changed in their local repositories.
we are focusing on bug fixing. check the bug list on sourceforge and take a look at the closed bugs over the last month or 2.
many of the remaining bugs are either not reproducible, or are in the process of being fixed.
cheers,
jonathan
Posts: 656
Joined: Jul 2004
Reputation:
2
i'm a bit puzzled regarding the versioning. a 2.0.0 release in general software terms to be implies tons of new features, but probably quite buggy. for a feature freeze wouldn't it make more sense to work on a 1.2 branch, and then have the 2.0 branch be where all the new features are introduced.
hoping for some progress here though :thumbsup:
i've held off on upgrading the last couple of months, hoping that the 2.0 would be 'around the corner'.
Posts: 91
Joined: Mar 2004
Reputation:
0
i stumbled upon this thread and i wanted to take the time to add my two cents about the 'planning' discussion.
it's fun to see how people want plannings and deadlines. to me plannings are just a way for bosses to stress the coders to code faster. i really enjoy those free projects where there are no dealines. everyone just codes when they want to and that's it, no one to tell you that it should have been done for yesterday. actually there are new versions everyday and it is really fun to see how the soft evolves.
i also think that it was a mistake from the coders side to annouce a feature-freeze and then change so much in the code. you put pressure on yourself for no obvious reason.
i also want to thank everyone working on this project (a thing that i don't usually do in 'work-posts').
so thank you for such a great work and dedication.
Posts: 3,805
Joined: Mar 2004
Reputation:
3
elupus
Team-XBMC Developer
Posts: 3,805
well.. the idea was to move from feature addition to code cleanup and bug fixing.. that some new features slip in will always happen, but it keeps the focus right. wich keeps us from scowering the feature suggest box for stuff to add.
Posts: 2
Joined: Jul 2006
Reputation:
0
I'm new to this XBMC project, and I really want to install it on my extra xbox. My only question is that, should I wait for 2.0.0, or will it not matter because it will be easy to upgrade from 1.1 to 2.0.0 (and because it will be many months before the next release)?
Thanks.
PS: I don't know if this is the right thread to ask this question, but I can't search for other topics, the search function for this forum can't find the simplest keywords.