On Wed, 4 Jul 2001, Curtis Veit wrote:
> Hi, I know I'm new to the list so my opinion is perhaps not so
> valuable. In fact I don't understand what ramifications an
> earlier release might have. Would the DirectX portion just be
> missing until next release or are there more drastic
> consequences?
No. What we have in CVS will come with the next release. We make
sure, that the code as robust as possible. Unstable/unfinished
stuff, like the DirectX-target are markt as "experimental -- use it
at your own risk".
> In any case I thought I'd share my viewpoint. I don't mind seeing
> releases more often. A full release without DirectX soon and a
> new point release with DirectX a month later doesn't bother me.
> In fact some of our engineers feel better shipping project that
> have had several point releases to fix bugs.
Yes. Our next release of libggi is version 2beta4. We wanna have a
rock-solid final 2.0 release.
> My intended use is to include the ggi library in the SDK we use
> at Lineo (At least for internal use for now.) It helps me to
> convince others to try GGI out if I can provide this earlier.
So go ahead, if you want.
> In order to get a new package into one of our releases we have a
> significant time between adding the package and testing the SDK
> before we can get it out to customers. For this reason I like
> seeing project point releases more often. I can get a package
> included and if there are any point releases before it goes to
> test and the new features are important I upgrade. (My management
> probably has a slightly different view of this.)
>
>
> The pitfall of always waiting for the next great feature before
> having a release is that sometimes the development takes longer
> than expected and the release date slips a long time...
>
> If you have full control over the development of the feature
> sometimes a small slip is OK. If you don't have control, expect
> a real delay.
Well, we have a control about the development, but no control about
the number of really active coders... :-( That's why the current
development is so slow... :-(
We really need more active coders!
> In my case I'll start by including the current snapshot anyway,
> so for now I'm fine, but a final release in the near future
> wouldn't hurt either.
Brian: Could you put together a TODO list for our 2beta4 release,
please?
CU,
Christoph Egger
E-Mail: [EMAIL PROTECTED]
