ready to release

[tom.baeyens]

all jira issues have been looked resolved or moved. code is tagged and ready to be released. please hold commits for a day and test the current HEAD of CVS. then we can release this version in tomorrow.

we'll continue to work on the HEAD branch towards 3.2.1 and 3.2.2. those releases will contain bug fixes and urgent feature requests only.

after that, we'll probably split a BRANCH_3_2 and start working on 3.3 on HEAD of CVS.

[dmlloyd]

In testing, I found a bug in the web console that will cause a stack trace if you try to filter your search. This was introduced with the change where I reset the session before the RENDER_RESPONSE phase. The fix is very simple though.

[tom.baeyens]

it would be great if you mentioned wether you actually fixed it or not.

i didn't see such change come in through cvs. i'm going to go ahead anyway. this problem is not worth stalling the release for. make sure you create a jira issue for it and fix it asap on HEAD so that it will appear in the release notes and so that we can point people to that issue in case they want more info about it.

[dmlloyd]

It's a 3-line fix, but I didn't commit it because you said not to commit anything...

[dmlloyd]

...but it's committed now.

[tom.baeyens]

good that it's fixed already. you did good to not commit it.

committing that last fix is often the causing other bugs in releases.

[jason.greene]

my early congratulations on this release :)