Board index » delphi » Proposal: Borland Patch Day (once a month)

2005-06-13 07:16:25 AM
delphi240
comments?
 

Max writes:
 

A never-ending patch cycle? No thanks. Once a product is stable I would like
it to just sit and mature.
My experience with software development is that you get your software
working with a certain set of libraries, compilers, components etc. Then
someone releases a new version and you have to QA everything again. If that
was happening every month, I would go insane.
I'd rather have QC accumulate work arounds, and serious bugs get patched.
Oliver Townshend
 

Max writes:
in a team, as a developer may have different patch with other
developers. 3rd party components may be affected with the patch.
If a problem with 3rd party components was found after several patches
had been applied, finding out which patch caused the problem is
difficult and takes time.
Wien.
--
blogs.slcdug.org/esaputra
Delphi Setting Manager - www.codeline.net
 

"Erwien Saputra" <XXXX@XXXXX.COM>wrote
 

Max writes:
ourselves. <g>
 

Max schrieb:
 

John Herbster writes:
But do they do that with their development tools?
Wien.
--
blogs.slcdug.org/esaputra
Delphi Setting Manager - www.codeline.net
 

"Alvaro GP" <XXXX@XXXXX.COM>writes
 

"Erwien Saputra" wrote
VB6 - released Jan 1996 - 6 service packs (SP) last one Apr 2004
VS.NET 2002 - released Apr 2002 - 1 SP released Mar 2005
VS.NET 2003 - released Jun 2003 - no SP released to date.
There has also been hot patches released from time to time usually aimed at
a specific problem and they are rolled into the next service pack. I don't
have the hot patch history for these development tools but IIRC they hasn't
been all that many.
On the whole it seems to me that VS.NET has a much better record than Delphi
2005 (3 SPs in 6 months) and to a large measure I attribute this to a slower
release cycle and the lengthly public beta program.
 

Hot fixes are the way to go. They are unofficial fixes that
if someone really needs it can use it and test it before it
makes it into an official fully tested SP. Lots of companies
do it with great success. What I like about hot fixes is
I get to choose whether I want to use it.
Max writes:
Thomas Miller
Wash DC Delphi SIG Chairperson
Delphi Client/Server Certified Developer
BSS Accounting & Distribution Software
BSS Enterprise Accounting FrameWork
www.bss-software.com
www.cpcug.org/user/delphi/index.html
https://sourceforge.net/projects/uopl/
sourceforge.net/projects/dbexpressplus
 

At 02:02:29, 13.06.2005, Alvaro GP writes:
--
Rudy Velthuis [TeamB] velthuis.homepage.t-online.de
"What do you take me for, an idiot?"
-- General Charles de Gaulle (1890-1970), when a journalist asked him if
he was happy
 

Imagine the posts on these groups:
Post: Problem with "blah blah blah" Using D205 Update 3 , Hotfixes #s
1,2,7,9,12
Reply: Try hotfix #3, 4
Post tried that, does not work.
Reply: Remove Hotfix #7 (casued problems for me) but apply hotfix #10 (in
which case remove hotfix #12 if you have less than 1 gigi of ram)
ond so it can go on and on...
"Thomas Miller" <XXXX@XXXXX.COM>writes

Oliver Townshend writes:
Workarounds are a mess and very costly. What if you also need to migrate
your code to a new version? Think CHOICE!
WRT Delphi..
IDE patches should not affect your code and patches can be (should be)
released frequently.
Compilers - the same thing. Read the change logs and see how it affects
you if (if at all) Use when you need it.
Releasing frequent patches creates more goodwill with your customers
than just sitting quietly and doing nothing and unfortunately B is in a
negative balance in this regard (e.g. Kylix in particular) :(
siegs
 

Francois Malan writes:
release.. you learn through experience.
siegs
 

Oliver Townshend writes:
in maintenance mode.
siegs