Past week a lot of tracker issues have been solved, we are getting close to the situation we want to be at…fix as much as possible bugs we can. Things we have done past week beside hunting down those bugs are:
- Last pieces of page caching, itemid and ftp layer coding has been done, results are now internally tested.
- Included the BEEZ template to show the power of the template engine and the MVC implementation creating an accessible and W3C compatible template.
We try to “meet” with the development working group members every week in IRC to talk about current status and progression. In the last meeting we were pretty sure we can release the beta-2 soon. We have decided to code freeze on March 10, after that only minor code changes (bug fixes) will be done. From that point on the other development working groups will be working on work that needs to be done to create a beta-2 package:
- Documentation will at least update the api-documentation and also will try to work on additional documentation.
- Marketing and media will work on new sample content.
- Quality and testing will perform some final tests.
We expect the working groups to finish up their work in around a week after the code freeze, and after that we can wrap up a beta-2 package.
What do we want to achieve with this second beta? The purpose of a beta is to collect as much as possible feedback on your code. This is exactly what we want everyone to do with this release, test it for us. The Quality and Testing work-group will do security, performance and functional test on the second beta. Because we have not done major security testing of the framework, we advise everyone not to use the second beta on production sites. The next stage in the development cycle will be a release candidate. This if there are indeed no major flaws in the framework.
No hay comentarios.:
Publicar un comentario