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]

I'll probably need an extra day to get all done.

[bernd_ruecker]

I am still not up to date with the latest changes and open issues, I hope to catch up today or Monday.

I still see big issues we need to tackle in the are of the Signavio Modeler (BPMN 2.0 format, SVG API, Encoding problems, …), but maybe most of it is already fixed. I will try to create ACT Issues for it to track it. But all of it would be vital to be included in the GA in my opinion. And we have to adjust the cycle remedies for the "old" BPMN format of Signavio to the latest stuff. And if everything works, we have to release a new jar for the signavo core components as well. Not sure if we make all of that till tuesday!

For Cycle itself we have some issues open, but since we tag it as "beta" (by a button on the logo now by the way), we can more easily postpone them to the next release. I try to come up with a plan for that till monday.

Cheers
Bernd

[bernd_ruecker]

Okay, here for me as documentation what needs to be done on the Modeler side:

- Todo http://jira.codehaus.org/browse/ACT-367: Release a new Maven version of the Signavio core components and upload them to the alfresco repository
- Signavio http://jira.codehaus.org/browse/ACT-366: Problems with Umlauts in Modeler
- Signavio http://jira.codehaus.org/browse/ACT-365: The BPMN 2.0 DI is still the early draft, not the spec version
- Check http://jira.codehaus.org/browse/ACT-335: Move modeler patching from demo setup to a dedicated build
- Check http://jira.codehaus.org/browse/ACT-290: SVG API should not peform access to Signavio Academic Version in the Internet
- Todo http://jira.codehaus.org/browse/ACT-368: Modeler gets patched multiple times
- Check http://jira.codehaus.org/browse/ACT-369: Modeler requires Java 6 to run
- Signavio http://jira.codehaus.org/browse/ACT-370: Signavio Core Components partially obfuscated?
- Check http://jira.codehaus.org/browse/ACT-363: Bug with relative paths in Modler Backend
- Signavio http://jira.codehaus.org/browse/ACT-371: Latest SVG API doesn't work with Activiti Modeler examples

I hope I found everything again….

P.S: I changed the list according to a new issue

[tombaeyens]

also in light of the potential refactoring of the configuration parsing ( http://forums.activiti.org/en/viewtopic.php?f=4&t=497 ), we'll delay the code freeze with 2 days and put it on thursday evening november 25.  This means that I plan to create the release branch on friday morning.  This code freeze will be for all involved parties (including us!).

[tombaeyens]

Focus now is turning towards documentation.  I propose that everyone works on a single chapter at a time to allow for as much concurrency as possible.  And that we use irc to let others know on which chapter we're working.  That should minimize the merging efforts.

[bernd_ruecker]

Hi Tom.
As written via Email, I will not have time for docs before saturday. So would merge that into the GA branch then, I hope that's still in time (but time after code freeze is for QA and docs, right?

[parul_vipparthi]

Hello Team,

I am still evaluating activiti, trying most of the bundled examples and playing around with it. I am sure you all are having a terrific time developing activiti, I really like this forum and thank you all for all the quick replies. 

I am sure many people like me are waiting for the release and I just wanted to wish you all good luck and celebrate the upcoming release.

Thank you all and have a great time!
parul
(Activiti User)

[tombaeyens]

@Bernd: Docs is not a problem.  But after today: let us know in this topic what you're going to do, which files are involved and notify us when you're done.

[falko_menge]

I could offer to do another aspell run on the documentation to fix any typos left after your reviews.

If want to run it on your own, this is the command I am using:
aspell –mode=html –add-html-skip=programlisting –add-html-skip=literal –dont-backup check ch13-Cycle.xml