Gamester17
2004-09-18, 20:51
xbmc feature freeze and bug bash!
we are happy to announce that we have now once again put the xboxmediacenter cvs (http://sourceforge.net/cvs/?group_id=87054) in a feature freeze and our second official xbmc public bug bash have begun, which is the first steps in the process of getting ready for another stable point release of xbmc. the cvs feature freeze stage implies that in order to not introduce new bugs no new features/functions coded should (preferably) be introduced into the cvs (http://sourceforge.net/cvs/?group_id=87054) until after the source code for the next point release have been set, this feature freeze will also give skinners a chance to catch up as xbmc's skin-structure is also locked down. in the mean time the official bug bash implies that we all should do our best to find and fix most bugs before the point release can be set. this also means that we now really need the publics help with xbmc development, we need you to update/translate strings.xml to all languages (http://www.xboxmediacenter.com/info_faq.htm#translations) (xbmc now support all foreign language characters through ttf-fonts (http://www.xboxmediaplayer.de/cgi-bin/forums/ikonboard.pl?act=st;f=1;t=6362)), plus find/troubleshoot bugs (http://www.xboxmediacenter.com/info_faq.htm#27) and most importantly submit them as very detailed bug reports on sourceforge.net bug tracker (http://www.xboxmediacenter.com/info_faq.htm#28), we of course also more than welcome other developers to help us of solve (http://cvs.sourceforge.net/viewcvs.py/xbmc/xbmc/bugs.txt?sortby=date) and submit fixes to those bugs (http://www.xboxmediacenter.com/info_faq.htm#28). only with your help can we get a xbmc 1.1.0 point release ready in a matter of weeks, however understand that all our team-members are volunteers so we can not set a definite deadline nor release date but we will do our best to try to have a release candidate ready within three weeks. *
we also like to remind you all that the xbmc project relies on your donations for its survival (http://www.xboxmediacenter.com/info_contrib.htm)!
please respect and understand that it is very hard to track or monitor bugs using a forum alone which is why our bug discussion forum (http://www.xboxmediaplayer.de/cgi-bin/forums/ikonboard.pl?act=sf;f=3) is not been meant for official "bug reporting (http://www.xboxmediacenter.com/info_faq.htm#27)", it's 'only' meant for a more general bug discussion. ex. if you don't know for sure that the problem symptom you are seeing is a bug or not then you should first post it in the forum for discussion, but if/once you are sure that what you are seeing is a bug (and you are using very latest cvs) then you should submit it as a clear and detailed bug report on our sourceforge.net bug tracker (http://www.xboxmediacenter.com/info_faq.htm#28) if you want it fixed.
note! for those who are new to xbmc, cvs (concurrent versions system) (http://sourceforge.net/cvs/?group_id=87054) 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 our xbmc faq (http://www.xboxmediacenter.com/info_faq.htm), thanks in advance.
we are happy to announce that we have now once again put the xboxmediacenter cvs (http://sourceforge.net/cvs/?group_id=87054) in a feature freeze and our second official xbmc public bug bash have begun, which is the first steps in the process of getting ready for another stable point release of xbmc. the cvs feature freeze stage implies that in order to not introduce new bugs no new features/functions coded should (preferably) be introduced into the cvs (http://sourceforge.net/cvs/?group_id=87054) until after the source code for the next point release have been set, this feature freeze will also give skinners a chance to catch up as xbmc's skin-structure is also locked down. in the mean time the official bug bash implies that we all should do our best to find and fix most bugs before the point release can be set. this also means that we now really need the publics help with xbmc development, we need you to update/translate strings.xml to all languages (http://www.xboxmediacenter.com/info_faq.htm#translations) (xbmc now support all foreign language characters through ttf-fonts (http://www.xboxmediaplayer.de/cgi-bin/forums/ikonboard.pl?act=st;f=1;t=6362)), plus find/troubleshoot bugs (http://www.xboxmediacenter.com/info_faq.htm#27) and most importantly submit them as very detailed bug reports on sourceforge.net bug tracker (http://www.xboxmediacenter.com/info_faq.htm#28), we of course also more than welcome other developers to help us of solve (http://cvs.sourceforge.net/viewcvs.py/xbmc/xbmc/bugs.txt?sortby=date) and submit fixes to those bugs (http://www.xboxmediacenter.com/info_faq.htm#28). only with your help can we get a xbmc 1.1.0 point release ready in a matter of weeks, however understand that all our team-members are volunteers so we can not set a definite deadline nor release date but we will do our best to try to have a release candidate ready within three weeks. *
we also like to remind you all that the xbmc project relies on your donations for its survival (http://www.xboxmediacenter.com/info_contrib.htm)!
please respect and understand that it is very hard to track or monitor bugs using a forum alone which is why our bug discussion forum (http://www.xboxmediaplayer.de/cgi-bin/forums/ikonboard.pl?act=sf;f=3) is not been meant for official "bug reporting (http://www.xboxmediacenter.com/info_faq.htm#27)", it's 'only' meant for a more general bug discussion. ex. if you don't know for sure that the problem symptom you are seeing is a bug or not then you should first post it in the forum for discussion, but if/once you are sure that what you are seeing is a bug (and you are using very latest cvs) then you should submit it as a clear and detailed bug report on our sourceforge.net bug tracker (http://www.xboxmediacenter.com/info_faq.htm#28) if you want it fixed.
note! for those who are new to xbmc, cvs (concurrent versions system) (http://sourceforge.net/cvs/?group_id=87054) 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 our xbmc faq (http://www.xboxmediacenter.com/info_faq.htm), thanks in advance.