[p4] Perforce 2006.1 - Time to upgrade?
Michael.Schlueter at secunet.com
Fri Jul 7 09:01:56 PDT 2006
We are using Perforce for more than five years now.
As far as I remember, the merge issue with 2005.2 was the first serious
bug in a released version in this five years.
I think that merge scenarios are the more complex thing a SCM system has
to deal with and it is very hard test all possible situations
But, because of the 2005.2 issue, I'm pretty sure that Perforce has
spend some effort, to prevent this from happening again.
However I tend to wait with the upgrade at least a few weeks until I get
a timeframe with low traffic to minimize the risk.
Additionally I have mirror system of our real perforce server and I
upgrade this one first and play I while with it.
Of course, someone has to be brave enough to go ahead, so I would
suggest that you update your server and tell us your findings ;-).
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of
> Weintraub, David
> Sent: Friday, July 07, 2006 3:03 PM
> To: perforce-user at perforce.com
> Subject: [p4] Perforce 2006.1 - Time to upgrade?
> I'm just curious about where Perforce tends to fall into this
> How has Perforce been in the past with new releases? How
> stable do they
> tend to be? Do you tend to upgrade as soon as possible to
> take advantage
> of the latest features? Do you wait a few months for Perforce to iron
> out any bugs? Or, do you avoid upgrading as long as possible?
> David Weintraub
> david.weintraub at bankofamerica.com
> david.weintraub at bofasecurities.com
> perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user