[MINC-development] Current release of MINC? New one needed I think...

[Andrew Janke]

Hi Matthijs,

Thanks for the offer, I see no one else has commented on this so I'm
going to presume that no-one else wants to put their hand up for this.
>From what I know of yourself and the group you are in, you will be
more than capable of taking care of this for us all.

I'll send you some details shortly of the release process I follow.
This will have changed a bit with the shift to cmake in MINC 2.2 but
will follow the same basic process.

The important parts are documented here but need updating to cmake parlance:

   https://github.com/BIC-MNI/minc/blob/master/README.release

ta


a



On 10 April 2014 05:59, Matthijs van Eede <matthijs at mouseimaging.ca> wrote:
> Hi all,
>
> I'm willing to take over the main release of MINC. I'm backed by and will have support from John Sled and Jason Lerch. There will be a couple of things I'll need to learn as I have not been involved in providing these kinds of releases before. And if you still want to use packages.bic.mni.mcgill.ca for future releases, I would need some sort of access to that.
>
> Cheers,
> Matthijs
>
> ----- Original Message -----
> From: "Andrew Janke" <a.janke at gmail.com>
> To: "MINC development discussion & planning" <minc-development at bic.mni.mcgill.ca>
> Sent: Tuesday, April 8, 2014 1:02:23 AM
> Subject: Re: [MINC-development] Current release of MINC? New one needed I       think...
>
> Hi Sean,
>
> I'm all for it. A number of people have changes in the current git
> tree that should be in a mainline release. Problem is that in the last
> year or so I've had far less spare time for MINC maintenance than I
> used to.
>
> So, if others are keen to take over the main release of MINC now might
> be a good time to hand over the reins of this, I have asked Vladimir
> about this already but didn't get a response. I've been looking after
> things for a number of years now and it's probably time to move on!
>
> I'll still be around and will contribute code and documentation and
> will help whoever volunteers to take over the main release duties for
> the 2.2 release. There are a few nuances around libtool versioning
> that should be adhered to for the upstream builds on
> debian/Ubuntu/Neurodebian/etc.
>
> ta
>
>
> a
>
>
> On 4 April 2014 06:38, Sean McBride <sean at rogue-research.com> wrote:
>> Hi all,
>>
>> What is the current release of MINC?
>>
>> This page:
>> <http://www.bic.mni.mcgill.ca/ServicesSoftware/MINC>
>>
>> says 2.0.18, which I know is old.  In this folder, the newest seems to be 2.2:
>> <http://packages.bic.mni.mcgill.ca/tgz>
>>
>> Which is from Sept 2012, pretty long ago.  In any case, I've just tried to build it and it doesn't even compile (at least with clang).  The compiler rightly complains:
>>
>> minc-2.2.00/libsrc2/hyper.c:769:11: error: non-void function 'miget_real_value_hyperslab' should return a value
>>       [-Wreturn-type]
>>           return;
>>           ^
>>
>> Might I suggest that a new release is in order? :)  Or is one expected to work from git?
>>
>> Thanks,
>>
>> --
>> ____________________________________________________________
>> Sean McBride, B. Eng                 sean at rogue-research.com
>> Rogue Research                        www.rogue-research.com
>> Mac Software Developer              Montréal, Québec, Canada
>>
>>
>> _______________________________________________
>> MINC-development mailing list
>> MINC-development at bic.mni.mcgill.ca
>> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
> _______________________________________________
> MINC-development mailing list
> MINC-development at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
> _______________________________________________
> MINC-development mailing list
> MINC-development at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development