2004-04-21, 17:03
xbmc reaches 1.0 beta, bug bash kick-off!
we are happy to announce the current xbmc cvs as 1.0 beta ready, thus our first official public bug bash has begun. as the time has come when xboxmediacenter finally starting to reach maturity we also like to declare that the era of xboxmediaplayer is over. the king is dead, long live the king! it's now time for xbmc to take the throne from its predecessor, so from today we officially do not support or develop xbmp any more; the xbmp forums will still be kept open but unmoderated, and development will only done on xbmc from now on. for those who missed it, xbmc/xboxmediacenter is our successor to xbmp/xboxmediaplayer, (yes both are/were developed by ourselves, the xbmp/xbmc-team), we have been working very hard on xbmc over the past 6 months and to show its readiness we have put together this xbmc vs. xbmp comparison chart, (which we will also try to keep up to date in the future).
xbmc now being beta also means we need the publics help with xbmc, as now more than ever do we need people to update/translate strings.xml to other languages, find/troubleshoot bugs and submit them as detailed bug reports on sourceforge.net bug tracker, we of course also welcome other developers to help us of solve and submit fixes to those bugs. know that we have now issued an official feature freeze during this beta stage so as to not introduce new bugs into the cvs code and also to let skinners catch up with the existing skin structure. so any new features coded during this beta stage should (preferably) not be introduced into the cvs before the source code for xbmc 1.0 (final) point release been set. only with your help can we get the first xbmc 1.0 release candidate ready in a matter of weeks.
to clarify all this for those who are new to this process and/or the xbmc-project:
- first was the alpha stage, which we now passed (during this stage loads of features were added and code was very buggy).
- now we are at the beta stage which comes before release candidates, during this stage we mostly concentrate on major bugs.
- then after the beta stage is over there will be release candidate(s) to be heavily tested to find small bugs and iron out details.
- after and when we are satisfied with last release candidate we will fix any last glitches and release that as the 1.0 point release.
note! for those who are new to xbmc, cvs (concurrent versions system) refers to the most current (day by day) source code.
ps! please do not post bugs, feature suggestion or support requests in this topic thread. read the xbmc faq, thanks in advance.
we are happy to announce the current xbmc cvs as 1.0 beta ready, thus our first official public bug bash has begun. as the time has come when xboxmediacenter finally starting to reach maturity we also like to declare that the era of xboxmediaplayer is over. the king is dead, long live the king! it's now time for xbmc to take the throne from its predecessor, so from today we officially do not support or develop xbmp any more; the xbmp forums will still be kept open but unmoderated, and development will only done on xbmc from now on. for those who missed it, xbmc/xboxmediacenter is our successor to xbmp/xboxmediaplayer, (yes both are/were developed by ourselves, the xbmp/xbmc-team), we have been working very hard on xbmc over the past 6 months and to show its readiness we have put together this xbmc vs. xbmp comparison chart, (which we will also try to keep up to date in the future).
xbmc now being beta also means we need the publics help with xbmc, as now more than ever do we need people to update/translate strings.xml to other languages, find/troubleshoot bugs and submit them as detailed bug reports on sourceforge.net bug tracker, we of course also welcome other developers to help us of solve and submit fixes to those bugs. know that we have now issued an official feature freeze during this beta stage so as to not introduce new bugs into the cvs code and also to let skinners catch up with the existing skin structure. so any new features coded during this beta stage should (preferably) not be introduced into the cvs before the source code for xbmc 1.0 (final) point release been set. only with your help can we get the first xbmc 1.0 release candidate ready in a matter of weeks.
to clarify all this for those who are new to this process and/or the xbmc-project:
- first was the alpha stage, which we now passed (during this stage loads of features were added and code was very buggy).
- now we are at the beta stage which comes before release candidates, during this stage we mostly concentrate on major bugs.
- then after the beta stage is over there will be release candidate(s) to be heavily tested to find small bugs and iron out details.
- after and when we are satisfied with last release candidate we will fix any last glitches and release that as the 1.0 point release.
note! for those who are new to xbmc, cvs (concurrent versions system) refers to the most current (day by day) source code.
ps! please do not post bugs, feature suggestion or support requests in this topic thread. read the xbmc faq, thanks in advance.
