topic Re: code freeze in Alfresco Archive

code freeze

tombaeyens — Fri, 23 Jul 2010 12:01:16 GMT

there are still 22 issues unresolved. (see link below) can everyone give an update on their situation? what issues can we expect to be resolved still? any issues that you thinkn you can't make by end of today? please give an update of the status.i plan to make the release branch somewhere on mon

Re: code freeze

tombaeyens — Fri, 23 Jul 2010 12:01:34 GMT

http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+ACT+AND+fixVersion+%3D+%225.0.alpha4%22+AND+resolution+%3D+Unresolved+ORDER+BY+assignee+ASC%2C+due+ASC%2C+priority+DESC

Re: code freeze

tombaeyens — Fri, 23 Jul 2010 12:06:41 GMT

My update:

i moved http://jira.codehaus.org/browse/ACT-6 to next release.

http://jira.codehaus.org/browse/ACT-6%20|Decide%20on%20Process%20Event%20Bus%20(PEB)%20architecture%20and%20integration will be done today probably.

Following issues i planned to do next week in the code freeze as they are more to do with docs and integration testing:
http://jira.codehaus.org/browse/ACT-9%20Add%20auto%20open%20of%20explorer%20after%20setup
http://jira.codehaus.org/browse/ACT-7%20Move%20logging.properties%20process%20activiti-engines-init%20to%20tomcat%20installation
http://jira.codehaus.org/browse/ACT-48%20Add%20Grails%20plugin%20link%20to%20docs%20or%20website

Re: code freeze

jbarrez — Fri, 23 Jul 2010 12:29:27 GMT

Following issues are documentation issues, which I plan to finish before Monday:

http://jira.codehaus.org/browse/ACT-12
http://jira.codehaus.org/browse/ACT-27

http://jira.codehaus.org/browse/ACT-40 is a package move issue. I've just send you a mail about it.

I will move (http://jira.codehaus.org/browse/ACT-15) to the next release, since I don't have enough time to finish it.

http://jira.codehaus.org/browse/ACT-47 will be assigned to you (bug we discussed yesterday about boundary events) and moved to next release. But first I need to add documentation to it, hence why I currently leave it on my name until I documented the known limitation.

So, when I cleaned my Jira, 5 issues will be removed from the 22.

Re: code freeze

bernd_ruecker — Fri, 23 Jul 2010 12:39:38 GMT

Question, since a lot of work is going on in cycle at the moment, shall we create a branch? Or do you create the branch for the release and we keep on committing in the trunk?

Re: code freeze

davidcognite — Fri, 23 Jul 2010 15:50:46 GMT

Sorry guys, I realised I've not been keeping JIRA current.

I've resolved the issues I've committed & updated the one I wasn't able to squeeze in.

David.

Re: code freeze

tombaeyens — Sat, 24 Jul 2010 06:50:48 GMT

@joram: and will you manage to finish those 5 next week without invalidating too much testing work next week?

@bernd: i'll create a release branch next week monday

@davidw: thanks

Re: code freeze

jbarrez — Sat, 24 Jul 2010 09:17:51 GMT

@Tom: read carefully, 3 of them I will resolve before Monday, 1 is postponed and 1 I will put on your name 😉

So I have all the time next week for testing

Re: code freeze

jbarrez — Mon, 26 Jul 2010 12:09:05 GMT

All my issues are resolved.

Re: code freeze

tombaeyens — Mon, 26 Jul 2010 13:56:18 GMT

ACT-30 Build the history data model
–> Initial code was committed. But the status is not yet far enough advanced to close it. So we keep this issue open in the next beta 1 release.

ACT-36 Revisit junit test support
–> I believe this was done so i resolved it.

ACT-44 MyBatis integration to allow user to share a SqlSession (or maybe just the Connection)
ACT-45 Finish transaction manager integration for Spring
ACT-46 Move Spring FactoryBean into Engine module Dave Syer
–> I believe these were intended for future releases. I assigned them to beta 1 release so that we can discuss them in context of the next release

ACT-32 Task notifications and reminders
–> postponing. should be discussed for plannning in beta1 release.

ACT-43 Add Process Event Bus infrastructure to the branch as the base for deciding on its architecture
–> During the meeting in Turnhout, Christian and Tom merged this on trunk.

ACT-9 Add auto open of explorer after setup
–> Postponed to beta 1. (upcoming pvm refactoring causes me to postpone this)

ACT-7 Move logging.properties process activiti-engines-init to tomcat installation
–> Postponed to beta 1. (upcoming pvm refactoring causes me to postpone this)

ACT-28 Decide on Process Event Bus (PEB) architecture and integration
–> Completed I think.

ACT-48 Add Grails plugin link to docs or website