brnached 5.0.beta1

[tombaeyens]

Hi,

I've created the release tag.  Trunk is 'free' again.

For next iteration, I'll try to create more clarity about the release cycle.  The goal for me is to get to a situation where releasing becomes less of a last minute challenge as it was this time 🙂

Tomorrow I'll set dates on JIRA freeze and code freeze.

JIRA freeze means that we agree on what will be worked on in the next release.  It's what we promise to the community.  So whatever we promise in the beginning should not be easily postponed.  (i realize this is going to be a challenge for us)  When you realize you won't be able to complete your issues by code freeze, make this clear as early as possible so that we can discuss how we'll deal with it.  I'll also inform about the status on all the jira issues a couple of days in advance.  At code freeze, trunk is frozen for a short period until a branch for the release is created.  After that manual QA is performed against the branch.  Only bug fixes should be committed to the release branch.

That's the theory that I have in my head.  I hope you all help me bringing this into practice 🙂   Tips and suggestions are welcome!

[davidcognite]

Hey Tom,

That sounds like a good plan. With the QA process, is it just yourself doing that? (obviously in addition to the testing we each do on the code we develop) Is there a set of test plans, or is it more ad hoc at this stage?

David.

[tombaeyens]

Our biggest focus is on automated tests. Apart from that, there is only the demo setup and a buy of ad hoc clicking in the webapps.

How hard would it be to create automated tests for the surf based webapps?

[davidcognite]

I wouldn't have thought it would be too tricky. Have a chat with Steve Rigby who heads up the Alfresco testing - I'm sure he'd be able to let you know exactly what's involved in setting up automated testing for the front end.

I think the hardest part would probably be deciding on and maintaining the test cases.