6.0.3 Release?

I was just curious to know if someone could enlighten us on the status of 6.0.3. Is 6141 it or will there be at least one more build?

Thank you,

Donald

10 comments
Comment actions Permalink

Hello Donald,

I was just curious to know if someone could enlighten us on the status
of 6.0.3. Is 6141 it or will there be at least one more build?


It won't be 6141 because 6141 doesn't have a proper release build packaging,
but right now we don't plan any additional fixes after 6141.

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Hi Dmitry,

As I checked, IDEA is updated to use latest version of SVNKit (aka javasvn) in build 6142 (http://www.jetbrains.net/jira/browse/IDEADEV-12898) not in build 6141 as your report: http://intellij.net/forums/thread.jspa?threadID=265141&tstart=0

We will have build 6xxx (>6142) as 6.0.3?

0
Comment actions Permalink

Sure it will be > 6141. What Dmitry was talking about was the fact, that no planned issues exist for 6.0.3.

0
Comment actions Permalink

Not even http://www.jetbrains.net/jira/browse/IDEADEV-12974 that you
fixed yesterday and marked 6.0.3?
Pretty please?
R

0
Comment actions Permalink

Robert, this is indeed fixed in 6.0.3. But it was not me, it was unknown developer:)

0
Comment actions Permalink

:)
and :D to the unknown developer!
R

0
Comment actions Permalink

Ehm, what about http://www.jetbrains.net/jira/browse/IDEADEV-11667 ? A co-worker just got this in 6141 (see below) and I think I've already seen this myself as well. Broken broken project-configuration functionality is a pretty bad thing IMHO. It would be great if you could sneak in another fix ;)



Sascha

0
Comment actions Permalink

Hello t800t8,

As I checked, IDEA is updated to use latest version of SVNKit (aka
javasvn) in build 6142
(http://www.jetbrains.net/jira/browse/IDEADEV-12898) not in build 6141
as your report:
http://intellij.net/forums/thread.jspa?threadID=265141&tstart=0


As mentioned multiple times in the forum, the "Fixed in build" file is filled
automatically by a script when a bug is marked as resolved. Thus, the value
in this field does not always correctly reflect the actual build number where
the issue was fixed.

As I was one of the developers responsible for this particular issue, I can
say with certainty that 6141 does include the latest svnkit.

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Hi Dmitry,

These files are in svn4idea/lib (in http://download.jetbrains.com/idea/idea6141.zip)
javasvn.jar: 1.10 MB (1,157,160 bytes)
javasvn-javahl.jar: 54.3 KB (55,676 bytes)

These files are in http://www.svnkit.com/org.tmatesoft.svn_1.1.0.standalone.zip
svnkit.jar: 1.04 MB (1,093,318 bytes)
svnkit-javahl.jar: 54.6 KB (55,915 bytes)

And you also forgot to update changelog.txt, it shows me the version of javasvn is 1.1.0 beta 2.

But thanks anyway, I can update it myself by deleting javasvn.jar, javasvn-javahl.jar and copy svnkit.jar, svnkit-javahl.jar to plugins directory.

0
Comment actions Permalink

Hello t800t8,

These files are in svn4idea/lib (I've got them from IDEA is packed in
ZIP file)
javasvn.jar: 1.10 MB (1,157,160 bytes)
javasvn-javahl.jar: 54.3 KB (55,676 bytes)
These files are in
http://www.svnkit.com/org.tmatesoft.svn_1.1.0.standalone.zip
svnkit.jar: 1.04 MB (1,093,318 bytes)
svnkit-javahl.jar: 54.6 KB (55,915 bytes)
And you also forgot to update changelog.txt, it shows me the version
of javasvn is 1.1.0 beta 2.

But thanks anyway, I can update it myself by deleting javasvn.jar,
javasvn-javahl.jar and copy svnkit.jar, svnkit-javahl.jar to plugins
directory.


As far as I know, the javasvn build included with the build 6141 is the latest
Subversion version of svnkit, which is newer than the release you got from
the Web site.

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com/
"Develop with Pleasure!"


0

Please sign in to leave a comment.