Patches
Hi,
Since interval between builds sometimes is long and sometimes current
build has some annoying bugs, wouldn't it be interesting to make IDEA
patchable? Such patch would fix a few most annoying bugs while JetBrains
work on the new features and minor bugs.
What do you think? Too BES-ed approach? :P
Franklin.
请先登录再写评论。
Franklin wrote:
As an EAP user, I woule love that (or nightly builds or anything), but I
guess it depends on the benefit for JetBrains.
The benefit as far as I am concerned for having patches or more builds
in addition to the "official" EAPs is to find problems closer to their
creation, as sometimes the developers have more fresh change information
and know how to isolate the problam that way.
But going back to my perspective as a developer using IntelliJ, the EAP
builds are a compromise between the level of QA or sanity they are run
through and the overhead that process is for JetBrains and their wish to
have functionality out and fixes to keep the buzz and feedback coming.
I can imagine that the builds we don't see as EAP builds are pretty beat
up on average because they don't go through the QA cycle needed for
public builds.
So JetBrains, if you can do this, it would be great if we could get
patches in cases where the bug is a big fat exception that is easy to
isolate (hopefully) if not more frequent (if of a 2nd degree of QA) builds.
Amnon
By the way only idea.jar, openapi.jar and resources.jar are changed frequently
Nightly builds would be nice, but they would have to disable the
exception reporting, etc because these should be considered bloody.
When the JSP 2.0 development starts, I would like hourly builds. :-P
Norris Shelton
Sun Certified Java Programmer
Franklin wrote:
>
>
>
Norris Shelton wrote:
True
Hey, how about inventing streaming binaries, i.e. you get an evolving
binary that is streamed all the time from somewhere instead of just
updates? All that without restarting the application (but of course!)...
Hey, what's that menu? I swear it wasn't there just a minute ago! :)
The problem with hourly/nightly builds is that you have to download the
whole .zip file. If it was a patch, you just needed to download a small
file that would replace a few .class files inside one of the IntelliJ
.jar files.
If we could download and apply the patches by selecting "Tools->Download
and apply available patches", it would be great!
Franklin.
Amnon I. Govrin wrote:
>> Nightly builds would be nice, but they would have to disable the
>> exception reporting, etc because these should be considered bloody.
>> When the JSP 2.0 development starts, I would like hourly builds. :-P
Franklin wrote:
Yup, true. It would be as easy as updating plug-ins.
+1!
Amnon
Hi,
Norris Shelton wrote:
It is started but very unstable (hint: it is developed as JSPX file
type). Please, wait one month more.
>> Hi,
>>
>> Since interval between builds sometimes is long and sometimes current
>> build has some annoying bugs, wouldn't it be interesting to make IDEA
>> patchable? Such patch would fix a few most annoying bugs while
>> JetBrains work on the new features and minor bugs.
>>
>> What do you think? Too BES-ed approach? :P
>>
>> Franklin.
--
Maxim Mossienko
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
Darn. That is what I figured. At that point, I will only be a week or
two away from QA.
At what point does the JSP file type get updated. I can't imagine why
anyone would want to suffer through the XML format.
Norris Shelton
Sun Certified Java Programmer
Maxim Mossienko wrote:
>
>
>> Nightly builds would be nice, but they would have to disable the
>> exception reporting, etc because these should be considered bloody.
>>
>> When the JSP 2.0 development starts, I would like hourly builds. :-P
>
>
>
>>
>> Norris Shelton
>> Sun Certified Java Programmer
>>
>>
>>
>>
>> Franklin wrote:
>>
>>> Hi,
>>>
>>> Since interval between builds sometimes is long and sometimes
>>> current build has some annoying bugs, wouldn't it be interesting to
>>> make IDEA patchable? Such patch would fix a few most annoying bugs
>>> while JetBrains work on the new features and minor bugs.
>>>
>>> What do you think? Too BES-ed approach? :P
>>>
>>> Franklin.
>>
>
>
Maxim - would this patching be an option then?
It doesnt have to be integrated (although that would be nice) - simplest solution is to provide a patch util to patch a JAR, along with the patches, or would patching the JARs break the obsfucator?
Take for example the rename variable refactoring that is broken in 3185. Ive actually rolled back to 3177 because of this issue - Im not testing any of the newer stuff in 3185, so 3185 is effectively an untested build from my standpoint - this clearly isnt beneficial to Jetbrains for EAP testing.
From what Ive seen, it's normally only a very small number of issues that stops an EAP build being useable by the majority.
JM2C,
Nick
You catched the point. Implementing patching is not possible due to obfuscator.
Most of the classes change their names from build to build.
Hi Maxim,
Please look at discussion
http://www.intellij.net/tracker/idea/viewSCR?publicId=20476
especially http://www.intellij.net/tracker/idea/viewSCR?publicId=20476#617110
TIA,
Dmitry
Well, it would be enough, if there would be soon fixes for the most annoying
bugs like the rename exception in 3185. Just curious, is it so much overhead
for you to release a new build or what is the reason, that the build numbers
increase to fast?
Tom