Will IDEADEV-6690 be fixed for final release?

Build 5646 still does not have this issue fixed - ie when working offline (on a laptop for example), the change markers do not appear and there is a multiple error messages about not finding the CVS server every time a file is saved. These issues are show stoppers for me and others I assume. What I have to do is keep 5.1.2 and use that when I take my laptop home and use the EAP build at work. I can't see how our company can upgrade to 6.0 if the problem is not fixed.

The reason I am worried is that there seems to be only a short time till 6.0 ships now and there has now been another new big VCS changes to allow background commits. However, people have raised valid questions about what happens if the file changes before the commit has occurred and should it be locked etc etc. This all seems like a lot of work to do in a short time.Was it really a good idea to introduce such a hige change will all the associated flow on effects so loate in the development cycle?

Can someone from IntelliJ put my mind at rest and tell me it will all be ok? Thanks.

4 comments
Comment actions Permalink

Hello Ian,

IB> Build 5646 still does not have this issue fixed - ie when working
IB> offline (on a laptop for example), the change markers do not appear
IB> and there is a multiple error messages about not finding the CVS
IB> server every time a file is saved. These issues are show stoppers
IB> for me and others I assume. What I have to do is keep 5.1.2 and use
IB> that when I take my laptop home and use the EAP build at work. I
IB> can't see how our company can upgrade to 6.0 if the problem is not
IB> fixed.

Yes, we definitely plan to address this issue before the final release.

IB> The reason I am worried is that there seems to be only a short time
IB> till 6.0 ships now and there has now been another new big VCS
IB> changes to allow background commits. However, people have raised
IB> valid questions about what happens if the file changes before the
IB> commit has occurred and should it be locked etc etc. This all seems
IB> like a lot of work to do in a short time.Was it really a good idea
IB> to introduce such a hige change will all the associated flow on
IB> effects so loate in the development cycle?

Background commits and updates may seem like a big thing externally, but
in fact the internal changes required for this feature were fairly small
and localized. Indeed, some extra work remains to be done to make sure that
it works correctly in all situations, but we will try to find simple and
reliable solutions for the possible problems. Thus, the impact of this new
feature on other VCS-related work is small.

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


0
Comment actions Permalink

Hi Dmitry,

Dmitry Jemerov wrote:

Background commits and updates may seem like a big thing externally, but
in fact the internal changes required for this feature were fairly small
and localized.


Would the changes for implementing background code inspection and
analysis be similarly small and localized? hint, hint, nudge, nudge;-)

Bas

0
Comment actions Permalink

Hello Bas,

>> Background commits and updates may seem like a big thing externally,
>> but in fact the internal changes required for this feature were
>> fairly small and localized.
>>
BL> Would the changes for implementing background code inspection and
BL> analysis be similarly small and localized? hint, hint, nudge,
BL> nudge;-)

Possibly, with one big "but": we'll have to make all the sources read-only
for the duration of the inspection run if the inspection profile includes
any global inspections.

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


0
Comment actions Permalink

Thats great! Thank you.

0

Please sign in to leave a comment.