Hi Rafa, Peter, As you both say this only works if the transitions are automated. > What about the Resolved>Closed? For continuous CI-releases like 2.40 we can > do that automatically, but is there an automated path for manual releases as > well? This is not done yet, but can certainly be automated and it is on our backlog (automatic release notes generation and after that issue closing).
We are right now in the process of introducing the CI automation that moves an issue from one status to another. In this case it would be for "Ready for review">"Ready for Testing". But before introducing the automation we wanted to raise this topic so that we can define what our ideal transitions are. > Is there a list of all the build and smoke tests that are performed before > moving from "Ready for testing" to "Ready for review"? Formally there is not. We have one documents with the early specs [1] and also a blog post [2] by Priya explaining the entire process. As a summary: * 2 incremental builds (PostgreSQL and Oracle). * 2 full builds. * A module installation/deinstallation test in command line. * API integrity check. * Database consistency check. * Various sanity checks. * 2 smoke tests. That's what we have right now. And what is planned for the next month: * Upgrade test from the latest MP to the latest CI generated OBX file. Both using the command line and with a graphical test. Thanks, Juan Pablo [1] http://wiki.openbravo.com/wiki/Promote_PI_to_Main#Job_specification [2] http://pmpearl.blogspot.com/2009/11/automatic-promotion-of-stable-code.html ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Openbravo-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openbravo-development
