Demetra: plea for more builds

I'd really like to see more builds to be published :( once every 1-2 weeks is not often enough IMHO.. although I understand that more builds out in the wild make it harder to track reported bugs.

6 comments

Hello Yann,

YC> I'd really like to see more builds to be published :( once every
YC> 1-2 weeks is not often enough IMHO.. although I understand that more
YC> builds out in the wild make it harder to track reported bugs.

Any arguments for this? We typically release builds when there is something
significant to test, and the new functionality is not badly broken. With
more frequent builds, you would get either more builds with few noticeable
changes, or more builds with broken or half-done features.

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


0

Well, everyone is free to evaluate a new build or wait for significant changes.

Sometimes just a single exception can make testing a build impossible or at least frustrating (Blame CVS Support, anyone?!), so it would provide JB with faster and more continuous feedback when such fixes are delivered more often.

Just my 2 cent..

0

Dmitry Jemerov (JetBrains) wrote:

Hello Yann,

YC> I'd really like to see more builds to be published :( once every
YC> 1-2 weeks is not often enough IMHO.. although I understand that more
YC> builds out in the wild make it harder to track reported bugs.

Any arguments for this? We typically release builds when there is
something significant to test, and the new functionality is not badly
broken. With more frequent builds, you would get either more builds with
few noticeable changes, or more builds with broken or half-done features.


Many of us would like to use Demetra here but we can't afford seriously
broken buggy builds. I think it would be great if you could release
builds frequently, but mark one build a week or two as "more stable."

0

Can we use Team Server of JetBrains, to get last builds? ;)

0

I'd agree with this - some of us here are happy to work with buggier builds, but having the option to use a slightly more stable build is a good idea.

0

I've "Blamed CVS Support" more times than I care to remember with 5218. At
least when I'm able to, sometimes it just deadlocks and I have to kill IDEA
(I've submitted a thread dump for that too). Generally the EAP builds have
been smoother than the 5.0 EAP, but CVS is currently badly broken to the
point where it's unusable for me. I'm looking forward to the next build,
but am happy enough to wait, it's EAP after all.

Well, everyone is free to evaluate a new build or wait for significant
changes.

Sometimes just a single exception can make testing a build impossible
or at least frustrating (Blame CVS Support, anyone?!), so it would
provide JB with faster and more continuous feedback when such fixes
are delivered more often.

Just my 2 cent..



0

Please sign in to leave a comment.