Re: Xcode and Confidentiality (was: xcode 2.2 editor problem)
Re: Xcode and Confidentiality (was: xcode 2.2 editor problem)
- Subject: Re: Xcode and Confidentiality (was: xcode 2.2 editor problem)
- From: Dave Camp <email@hidden>
- Date: Tue, 8 Nov 2005 11:36:07 -0800
On Nov 8, 2005, at 4:43 AM, Greg Hurrell wrote:
El 08/11/2005, a las 0:45, Chris Espinosa escribió:
2.2DP1 is available to online members. Other seeds are available
to various other people according to their ADC status. But the
key here is that the existence of 2.2 is not under nondisclosure,
so merely mentioning the version number in a message on xcode-
users is not a violation of NDA, as several people here implied.
But discussing the details of 2.2 seeds is.
I have a general question about these seeds. I am only a small
developer, so I do all of my work on a single, production machine.
I don't have the luxury of a second "test" machine to install pre-
release seeds on. I almost exclusively only use final releases,
even though I would often *like* to do testing on pre-releases
(especially seeds of the OS itself) to make sure that my software
still works on it.
What stance do other developers in my situation adopt with respect
to trying out these new Xcode builds? I know that the use of pre-
release software is always a "use at your own risk" affair, but I'm
wondering how many decide to actually run that risk on their
production machines. Thoughts?
I almost always install them. Usually they work fine and I find the
bug fixes or new features improve my workflow. If it turns out to be
buggy, reverting back isn't too difficult. In my case I'm doing a lot
of Intel porting, so I need the new releases anyway...
Dave
---
You are in a maze of testy little Java VMs, all subtly different.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden