[Dcmlib] static ::New() / Factory

[Mathieu Malaterre]

Ok I know I should be very ashamed but seriously could it be notified 
somewhere, like the News section or at least the changelog. Who is in 
charge to do the tarball/binaries ?

I would like to yank jasper from any release since it does not work, I 
don't want people to even see jasper was in gdcm at some point. So I'll 
be working on 1.2 to clean it up. As a side note I'd like to remove 
jasper today from CVS HEAD. And move openjpeg to gdcm 1.2.

Thanks
Mathieu

Benoit Regrain wrote:
> See your tag branch !!!
> Version1_2_bp...
> oooh... a tag branch...
> All new version must have its tag / branch. And I have done it.
> 
> Benoit
> 
> 
> ----- Original Message ----- From: "Mathieu Malaterre" 
> <mathieu.malaterre at kitware.com>
> To: "Benoit Regrain" <benoit.regrain at creatis.insa-lyon.fr>
> Cc: "Mailing list gdcm" <dcmlib at creatis.insa-lyon.fr>
> Sent: Monday, November 14, 2005 3:12 PM
> Subject: Re: [Dcmlib] static ::New() / Factory
> 
> 
>>
>>> I would that gdcm goes up and integrates the changes that we have 
>>> speaken 6 month ago.
>>
>>
>> And I would like to be inform, or at least have a branch to intergate. 
>> It has been merge in the middle of CVS HEAD ... I now have to wait 
>> until the API stabilize (well will it ever?) to integrate into ITK.
>>
>> You cannot break the API so heavily without prior notice, or a CVS 
>> Tab/branch... please !
>>
>> Thanks for listening to my complains...
>> Mathieu
>> Ps: So ITK is stuck with gdcm 1.0 for quite a while...
>> _______________________________________________
>> Dcmlib mailing list
>> Dcmlib at creatis.insa-lyon.fr
>> http://www.creatis.insa-lyon.fr/mailman/listinfo/dcmlib
> 
> _______________________________________________
> Dcmlib mailing list
> Dcmlib at creatis.insa-lyon.fr
> http://www.creatis.insa-lyon.fr/mailman/listinfo/dcmlib
>