Redmine

I'm finding that on trunk the lock_version of the Issue model isn't being taken into account, meaning that different users can make conflicting changes to issues without any notice from redmine.

I've only had a cursory look at the source, but it looks like lock_version should perhaps be a safe attribute (see r3308), otherwise it never gets set from the request params.

Additionally (perhaps this should be a different bug?) once the lock_version is accepted as a safe attribute, the stale object exception handler in IssuesContoller::update attempts to read a non-existant variable 'attachments'. It looks like that variable was refactored away to the Issue model in r3545