0
Quote
Hi everyone,
phpBB "Olympus", otherwise known as phpBB 3.0.0 is nearing its initial beta release and we decided to open our bug tracker for reporting issues with CVS now. The aim of the opening of the bug tracker is so that advanced users already having a current CVS copy working or those able to cope with installing and maintianing a CVS copy, may now report problems they encountered.
We want to identify problems with "Olympus" now, before we release a public beta. This has the advantage of us being able to change the code without providing an update path and in turn then hopefully being able to provide an update path during the betas.
For all of you not wanting to install a half-finished product (it is actually pre-alpha code still), we have compiled a list of features "Olympus" is having currently. We also strongly discourage the use of "Olympus" in live environments.
Who should report bugs
Everyone comfortable with manual database work, editing of PHP files and willing to help spot the most obvious bugs.
What happens to reports about unfinished features
Reports about unfinished features are most likely to be tagged as "Review Later" which means that we will revisit the bug report at a later stage. The same tag will be used for reports we are not able to handle "immediately" and need to revisit after having finished or cleaned up other parts of the code.
Are there any items being more important?
Since we develop with MySQL primarily, it would be nice if there are people competent with other DBMS than MySQL. For example a person testing "Olympus" with Oracle would help us greatly to identify SQL layout and syntax problems. The currently supported DBMS are:
Firebird (firebird) - Firebird 1.5+/Interbase 7.1+
MSSQL (mssql) - MSSQL 2000+
MSSQL through ODBC (mssql_odbc) - MSSQL 2000+
MySQL (mysql) - MySQL 3.23+/4.0+/4.1+
MySQL4 (mysql4) - MySQL 4.0+/4.1+/5.0+
MySQLi (mysqli) - MySQL 4.1+/5.0+
Oracle (oracle)
PostgreSQL (postgres) - PostgreSQL 7.3+
SQLite (sqlite)
If you are working with one of those DB's daily and also being competent in PHP, you are invited to contact me by PM too. We want to work close with these DB Experts to make Olympus a pleasure experience on every DB.
Are we able to report security related problems?
Yes, we even ask for those reports - though please use our security tracker for reporting security related issues with "Olympus".
Links
Olympus Bug Tracker
Security Tracker
Area51 - phpBB Development
Daily Snapshots/CVS Information
KB Article on how to use CVS
Non-exhaustive Olympus Feature List
And when do we get the beta now?
We hope the bug tracking phase to last at least a few weeks, since we need to finish some areas and features before we are able to release a public beta. Depending on the issues arising due to the reportings we may expand this further.
Thanks everyone and happy reporting.
phpBB "Olympus", otherwise known as phpBB 3.0.0 is nearing its initial beta release and we decided to open our bug tracker for reporting issues with CVS now. The aim of the opening of the bug tracker is so that advanced users already having a current CVS copy working or those able to cope with installing and maintianing a CVS copy, may now report problems they encountered.
We want to identify problems with "Olympus" now, before we release a public beta. This has the advantage of us being able to change the code without providing an update path and in turn then hopefully being able to provide an update path during the betas.
For all of you not wanting to install a half-finished product (it is actually pre-alpha code still), we have compiled a list of features "Olympus" is having currently. We also strongly discourage the use of "Olympus" in live environments.
Who should report bugs
Everyone comfortable with manual database work, editing of PHP files and willing to help spot the most obvious bugs.
What happens to reports about unfinished features
Reports about unfinished features are most likely to be tagged as "Review Later" which means that we will revisit the bug report at a later stage. The same tag will be used for reports we are not able to handle "immediately" and need to revisit after having finished or cleaned up other parts of the code.
Are there any items being more important?
Since we develop with MySQL primarily, it would be nice if there are people competent with other DBMS than MySQL. For example a person testing "Olympus" with Oracle would help us greatly to identify SQL layout and syntax problems. The currently supported DBMS are:
Firebird (firebird) - Firebird 1.5+/Interbase 7.1+
MSSQL (mssql) - MSSQL 2000+
MSSQL through ODBC (mssql_odbc) - MSSQL 2000+
MySQL (mysql) - MySQL 3.23+/4.0+/4.1+
MySQL4 (mysql4) - MySQL 4.0+/4.1+/5.0+
MySQLi (mysqli) - MySQL 4.1+/5.0+
Oracle (oracle)
PostgreSQL (postgres) - PostgreSQL 7.3+
SQLite (sqlite)
If you are working with one of those DB's daily and also being competent in PHP, you are invited to contact me by PM too. We want to work close with these DB Experts to make Olympus a pleasure experience on every DB.
Are we able to report security related problems?
Yes, we even ask for those reports - though please use our security tracker for reporting security related issues with "Olympus".
Links
Olympus Bug Tracker
Security Tracker
Area51 - phpBB Development
Daily Snapshots/CVS Information
KB Article on how to use CVS
Non-exhaustive Olympus Feature List
And when do we get the beta now?
We hope the bug tracking phase to last at least a few weeks, since we need to finish some areas and features before we are able to release a public beta. Depending on the issues arising due to the reportings we may expand this further.
Thanks everyone and happy reporting.
Official Article: http://www.phpbb.com...p?f=14&t=375510
dEcade
lol.
