Hello Tim,
  Are you sure about this weekend ?

--
Charalampos Michael - [Creation Power] - http://www.creationpower.gr

Michael,

<< Are you sure about this weekend ? >>

If we get new bug reports in before a new build goes out, the build will be
held up until I can confirm/clear the new bug reports.  That is why new
builds and releases are often not ready when I estimate that they will be.
This is done to keep the number of builds to a minimum.

Right now it looks like I will finally be able to get the new build going
tonight.

--
Tim Young
Elevate Software
www.elevatesoft.com

Dear Tim,

> If we get new bug reports in before a new build goes out, the build will be
> held up until I can confirm/clear the new bug reports.  That is why new
> builds and releases are often not ready when I estimate that they will be.
> This is done to keep the number of builds to a minimum.
>
> Right now it looks like I will finally be able to get the new build going
> tonight.

Well, why don't you release a build every week instead of waiting
adding new fixes every time you get a report which can take up to a
month as it seems ?

Eg, the past week you fixed 5 bugs and have 3 waiting.
Release an EDB build with the 5 bug fixed and proceed the next
week with the other 3 bugfixes.

I don't care about build numbers, i care to continue my work
as soon as possible because i need to deliver it in order get
payed.

As you may know the we're depending on EDB fixes to continue work
on our projects because EDB is one of the core components.

Thank you for understanding

--
Charalampos Michael - [Creation Power] - http://www.creationpower.gr

Michael,

<< Well, why don't you release a build every week instead of waiting adding
new fixes every time you get a report which can take up to a month as it
seems ? >>

Look, it usually takes a couple of days to do a new build in terms of prep
work, testing, etc..  If I did a new build every week, I'd have two less
days to work on other things.  As for taking a month, it really depends upon
the build and what is going on.  You reported a bug 10 days ago, and I'm
doing a new build today.  What exactly is the problem ?  Are you saying that
10 days is too long for an entire new build ?

<< I don't care about build numbers, i care to continue my work as soon as
possible because i need to deliver it in order get
payed.

As you may know the we're depending on EDB fixes to continue work on our
projects because EDB is one of the core components. >>

Yes, I understand, and this is the case with *every single ElevateDB
customer*, not just you.  Which is why I need to make sure that any
outstanding bugs are fixed immediately for *everyone*.

--
Tim Young
Elevate Software
www.elevatesoft.com

Dear Tim,

> << Well, why don't you release a build every week instead of waiting adding
> new fixes every time you get a report which can take up to a month as it
> seems ? >>
>
> Look, it usually takes a couple of days to do a new build in terms of prep
> work, testing, etc..  If I did a new build every week, I'd have two less
> days to work on other things.  As for taking a month, it really depends upon
> the build and what is going on.  You reported a bug 10 days ago, and I'm
> doing a new build today.  What exactly is the problem ?  Are you saying that
> 10 days is too long for an entire new build ?

Well, It's 10 days doing nothing and waiting for a fix.

1) My propose was to do hotfixes and don't promise release dates.
2) Or send the fix only
3) And keep older builds on the website for download. At least 2 build
before. Eg, build 5, build 6 and the latest build 7

Eg, for my bug reports i found that build didn't have them so currently
i use Build 6 but because i kept it and didn't erase it ...

I understand how complex is the code but sometime a fix brokes other
things and that's why i insist to have 2 earlier builds on your website.

> << I don't care about build numbers, i care to continue my work as soon as
> possible because i need to deliver it in order get
> payed.
>
> As you may know the we're depending on EDB fixes to continue work on our
> projects because EDB is one of the core components. >>
>
> Yes, I understand, and this is the case with *every single ElevateDB
> customer*, not just you.  Which is why I need to make sure that any
> outstanding bugs are fixed immediately for *everyone*.

Yes, so keeping older builds for download into your website will be
the solution ...

--
Charalampos Michael - [Creation Power] - http://www.creationpower.gr

Michael,

<< Well, It's 10 days doing nothing and waiting for a fix. >>

I understand, but sometimes these things can't be helped.

<< 1) My propose was to do hotfixes and don't promise release dates.
2) Or send the fix only >>

I can't give out fixes without testing them, and I can't test them without
adding a new test to the test framework.  Any new test needs an incident
report entered in also.  You see where I'm going with this ?

<< 3) And keep older builds on the website for download. At least 2 build
before. Eg, build 5, build 6 and the latest build 7 >>

If you ask, we're always happy to send you an older build that you need.
I'll make a note to include older builds on the new web site, however.

<< Yes, so keeping older builds for download into your website will be the
solution ... >>

Yes, that looks like the best option.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

>If you ask, we're always happy to send you an older build that you need.
>I'll make a note to include older builds on the new web site, however.

On their own separate page (or pages) though please. Trying to spot my Delphi versions is difficult enough as it is. How you cope even with automation to keep them all separate is a minor miracle. I'm sure one day soon I'm going to download the D2006 version and find that's fine for queries but tables require Lazarus

Roy Lambert

Roy,

<< On their own separate page (or pages) though please. Trying to spot my
Delphi versions is difficult enough as it is.  >>

Hopefully some day we can trim them down a bit, but I'll make a note to make
that whole thing easier to read.  The grids are going away in a lot of
cases.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim


><< On their own separate page (or pages) though please. Trying to spot my
>Delphi versions is difficult enough as it is. >>
>
>Hopefully some day we can trim them down a bit, but I'll make a note to make
>that whole thing easier to read. The grids are going away in a lot of
>cases.

As I indicated; you have my sympathy. I just have to download them occasionally, you have to work with them.

Roy Lambert

Roy,

<< As I indicated; you have my sympathy. I just have to download them
occasionally, you have to work with them. >>

Yeah, I literally have about 20 IDEs and development environments installed
on my development machine, including Delphi 5-2010, C++Builder 5-2010,
NetBeans, VS 2003-2010, and Lazarus.

--
Tim Young
Elevate Software
www.elevatesoft.com