Code freeze coming up

[tombaeyens]

Hi Guys,

Next week tuesday is the code freeze for 5.0.ga.  Is everyone on schedule?

http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+ACT+AND+resoluti...

Previous iterations we created some confusion around the code freeze date.  I want to fix this starting this release:  We discuss the code freeze time in this topic.  We have a max of 2 days that we could potentially postpone the code freeze date.  But when we freeze, the release branch will be created immediately and development on trunk will be able to continue quickly.  In other words, we won't apply different regimes for us then for the rest of the community.

[jbarrez]

And I always thinking that you are so awesomely literate 😉

[tombaeyens]

tomb: hi all
[10:21] tomb: we'll postpone the codefreeze till this evening
[10:22] tomb: we only have docs issues outstanding, except for one thing that we discovered yesterday
[10:22] tomb: well… and thing is a build issue thing, so also not a conding thing
[10:23] tomb: i'll update the layout of the workspace/activiti-engine-examples and  workspace/activiti-spring-examples
[10:23] tomb: and i'll be adding a build file to those projects
[10:24] tomb: so that our users get a build file with which they can deploy the classes and processes
[10:24] tomb: i'll be doing that today
[10:24] tomb: and then branch this evening or tomorrow morning

[tombaeyens]

postponing the code freeze with another day (till saturday evening) as the build scripts are not completely finished and because Hudson http://178.77.67.242:8080/  is not totally green yet.

[bernd_ruecker]

@Cycle Team: Please don't feel tempted to commit stuff even with that extra day. I will do all the testing tomorrow, so please commit only Bug fixes and let me know what you have done (done by a proper commit message :-)). Thanks!

[tombaeyens]

created release branch https://svn.codehaus.org/activiti/activiti/tags/activiti-5.0

[tombaeyens]

All commits on https://svn.codehaus.org/activiti/activiti/tags/activiti-5.0 MUST have a Jira issue associated.
And permission to commit on that tag has to be asked upfront.

So when you want to change something on that branch/tag, the procedure is create a Jira, describe as clear (and brief) as possible what exactly you want to change.  Then send it to me (tom) and wait for my go ahead before committing.

Thanks.