TC 4.0 (Calcutta) Release Date and Eclipse Delayed Commit?

Greetings:
I was wondering if there is a planned release date for TC4.0

My preference would be for a smaller release to deal with ALL the outstanding Eclipse Plugin issues. Specifically http://jetbrains.net/jira/browse/TW-3625

Sorry for the rant :)

Please correct me if I am wrong about anything, but here has been my experience.

We have spent the last while trying to get Delayed commit to work for us only to find out that there are differences in how delayed commit is implemented between the IDEA and Eclipse.

When reading the literature and blogs about delayed commit, the ability to submit a change set and then continue to work on the same files is a great feature and is highlighted often. However it is not clearly specified that eclipse does not have this ability.

The eclipse plugin should make our life easier than it is with Subclipse.
Based on a summary of some of the existing tracker issues I would love to see the following functionality:
1 - The user should be prompted to do delayed commit if they try to commit direct to SVN.
2 - The plugin should show a list of previous commit messages (like almost every other VCS tool)
3 - When starting a Delayed Commit, the user should have the ability to add unversioned files (like you can in Subclipse)
4 - When starting a delayed commit, the user should be able to merge and or deal with svn conflict before the run.
5 - If the test run is a success, but there is a conflict, the user should be allowed to edit conflicts and merge the problem files and force commit OR re-run the newly modified changeset.
6 - It would be great if the plugin issues could be release as TC 3.2 instead of waiting for 4.0.

We love the TC Server and remote runs, but I am having a hard time selling Delayed commit to my team given that they can lose a change set if the build fails for any reason (conflict or otherwise). If they prepare a unit of work, submit a delayed commit, start working on the same files, and then the commit fails, they have to wait until they are ready to commit again. Many feel that if they have to wait to get the status of the commit from TC, they might as well just run all the tests on their workspace and commit.

Without a viable delayed commit (for eclipse), that puts TC in line with Pulse. My vote is for TC, but as group we have to look at other products.
It would be very helpful if someone from Jetbrains could outline the future plans for the Eclipse Plugin.

I was longtime and happy IDEA user and would love to use now. In my current company however, switching from Eclipse is not going to happen. So I really would love to see the Eclipse plug get "bullet proofed" as soon as possible.

Thanks for the taking the time to read this..

2 comments

Hello,

At the moment the planned date of TC 4.0 is still unknown. However we expect
it to be in this year. Chances are that we will release some kind of a
milestone in summer. As for Eclipse plugin it is obvious for us that we need
to bring its functionality to the level of IDEA plugin. Now I can only
suggest you to submit your suggestions in our tracker, we will certainly
address them in the next version.

--
Pavel Sher
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"



"jmychasiw" <no_reply@jetbrains.com> wrote in message
news:15886207.1205252037738.JavaMail.itn@is.intellij.net...

Greetings:
I was wondering if there is a planned release date for TC4.0

>

My preference would be for a smaller release to deal with ALL the
outstanding Eclipse Plugin issues. Specifically
http://jetbrains.net/jira/browse/TW-3625

>

Sorry for the rant :)

>

Please correct me if I am wrong about anything, but here has been my
experience.

>

We have spent the last while trying to get Delayed commit to work for us
only to find out that there are differences in how delayed commit is
implemented between the IDEA and Eclipse.

>

When reading the literature and blogs about delayed commit, the ability to
submit a change set and then continue to work on the same files is a great
feature and is highlighted often. However it is not clearly specified
that eclipse does not have this ability.

>

The eclipse plugin should make our life easier than it is with Subclipse.
Based on a summary of some of the existing tracker issues I would love to
see the following functionality:
1 - The user should be prompted to do delayed commit if they try to commit
direct to SVN.
2 - The plugin should show a list of previous commit messages (like almost
every other VCS tool)
3 - When starting a Delayed Commit, the user should have the ability to
add unversioned files (like you can in Subclipse)
4 - When starting a delayed commit, the user should be able to merge and
or deal with svn conflict before the run.
5 - If the test run is a success, but there is a conflict, the user should
be allowed to edit conflicts and merge the problem files and force commit
OR re-run the newly modified changeset.
6 - It would be great if the plugin issues could be release as TC 3.2
instead of waiting for 4.0.

>

We love the TC Server and remote runs, but I am having a hard time selling
Delayed commit to my team given that they can lose a change set if the
build fails for any reason (conflict or otherwise). If they prepare a
unit of work, submit a delayed commit, start working on the same files,
and then the commit fails, they have to wait until they are ready to
commit again. Many feel that if they have to wait to get the status of
the commit from TC, they might as well just run all the tests on their
workspace and commit.

>

Without a viable delayed commit (for eclipse), that puts TC in line with
Pulse. My vote is for TC, but as group we have to look at other products.
It would be very helpful if someone from Jetbrains could outline the
future plans for the Eclipse Plugin.

>

I was longtime and happy IDEA user and would love to use now. In my
current company however, switching from Eclipse is not going to happen.
So I really would love to see the Eclipse plug get "bullet proofed" as
soon as possible.

>

Thanks for the taking the time to read this..



0

Thanks for the update. We look forward to new additions to the plugin.

0

Please sign in to leave a comment.