| Jesper Veggerby Hansen 2005-10-22, 7:56 am |
| Hi Michael,
There really isn't any fixed timeline or roadmap for this. The reason it
is still alpha is not due to stability (it is my impression that most
installations run smooth - but I understand your concerns with having
alpha code in production), but mainly because of the dependency for
Image_Canvas. We cannot go beta unless Image_Canvas is beta, and it is
still alpha because:
1) It is a very "young" package
2) Image_Graph is the only package depending on it, and since IC was
thought of as a general purpose package, going beta might lock the API
too much due to BC requirements. And if we go beta on Image_Canvas it
could be that future packages cannot adopt Image_Canvas due to the API
was "locked" pre-maturely, and they would implement their own driver
mechanism (if any). This would of course ruin the idea of having a
common drive, which will improve (possible) interoperability between
Image_* packages.
I will be happy the day we announce Image_Graph stable (I think it _is_
at least beta quality at this point, and will of course go through a
beta stage before going stable), but I would also like to keep the door
open for future Image_* packages adopting Image_Canvas.
BR
/Jesper
Michael Dwyer wrote:
> Hi,
>
>
>
> Is there a general time frame when I might expect the Image_Graph
> package to move beyond the alpha release stage? Stable would be nice,
> but even beta would be OK. Not that I have found problems, I am just
> wary of doing any serious work with a major dependency on an alpha-level
> package.
>
>
>
> Thanks!
>
>
>
> Mike Dwyer
>
> Programmer/Analyst
>
> San Diego Supercomputer Center
>
> 9500 Gilman Dr. # 0505
>
> La Jolla, CA 92093-0505
>
> 858-822-5489
>
>
>
>
|