we have detected a subtle bug in the Perforce plugin. The following happened:

• We have a release codeline R which has been branched from the main code line M some time ago.
• Now a developer had to make a bugfix in R. The fix included adding a new File "F.java".
• The developer submitted his changes into R and afterwards integrated the changelist into M.
• But before submitting into M the developer had to make some additional changes to "F.java", so he
  simply opened the class in IDEA and did the changes.
• Then he submitted everything into Perforce.

Now the problem showed up: although the developer made some changes to "F.java" those changes where lost,
i.e. the Perforce depot only contained the version of "F.java" that was also submitted to the release codeline
R!

Our Perforce experts told me, that one has to do a "reopen for edit" on newly created files like "F.java" in
case one wants to edit them before submit. Obviously the IDEA Perforce plugin did not do that, but simply
seemed to remove the write protection on the file.

In our particular case we could easily detect, that something went wrong, since the build of the codeline
failed after the changelist had been submitted. However in other cases this bug may have severe impacts in
case changes may be lost.