Strange version behavior after bulk import

[deisenlord]

I've been using alfresco for about a month preparing to use it as a replacement for a SharePoint installation.  I've uploaded a set of version for a file using the bulk file system up loader.   This works perfectly fine although the the sequence of versions is a little odd.   It starts and one and in my case goes up to 83.0 and then the "head" or latest revision is stored as 83.1.   Now the really strange part.  If I add a new version via the share gui and say a new minor version (it says 83.2), it creates an 83.2, 83.3, 83.4 and the latest version 83.5 !!!!  

I know it must sound like I'm smoking something but to assure you I'm not so I have included screen grabs.

Before
[img]http://www.davideisenlord.com/bucket/before.JPG[/img]

After
[img]http://www.davideisenlord.com/bucket/after.JPG[/img]

Any ideas?

[afaust]

Hello,

dou you have any logic (rules, policies, addons) in your system that may include versioning behavior? Usually, during one transaction, one version at most is created unless some code explicitly calls the VersionService to create explicit versions, i.e. in a workflow it may be required to create multiple versions of the same document in the same transaction as part of different activities.

Regards
Axel

[deisenlord]

No, bone stock installation of 4.2d.  I had to go to D from C as it has a showstopper versioning problem with locking which prevents you from uploading multiple versions.

[deisenlord]

Just searched on JIRA, unbelievable but a known bug.

JIRA implies it's fixed in 4.2D but its clearly not.