From sean at rogue-research.com  Thu Apr  3 16:38:13 2014
From: sean at rogue-research.com (Sean McBride)
Date: Thu, 3 Apr 2014 16:38:13 -0400
Subject: [MINC-development] Current release of MINC? New one needed I
	think...
Message-ID: <20140403203813.435581257@mail.rogue-research.com>

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



From vladimir.fonov at gmail.com  Thu Apr  3 18:48:21 2014
From: vladimir.fonov at gmail.com (Vladimir S. FONOV)
Date: Thu, 03 Apr 2014 18:48:21 -0400
Subject: [MINC-development] Current release of MINC? New one needed I
 think...
In-Reply-To: <20140403203813.435581257@mail.rogue-research.com>
References: <20140403203813.435581257@mail.rogue-research.com>
Message-ID: <533DE535.9070804@gmail.com>

Hello,

yes, the new release is in order : can you make this 
https://github.com/BIC-MNI/libminc/tree/develop  into a new release ?


On 14-04-03 04:38 PM, Sean McBride 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,
>


-- 
Best regards,

  Vladimir S. FONOV ~ vladimir.fonov <at> gmail.com

From a.janke at gmail.com  Tue Apr  8 01:02:23 2014
From: a.janke at gmail.com (Andrew Janke)
Date: Tue, 8 Apr 2014 15:02:23 +1000
Subject: [MINC-development] Current release of MINC? New one needed I
	think...
In-Reply-To: <20140403203813.435581257@mail.rogue-research.com>
References: <20140403203813.435581257@mail.rogue-research.com>
Message-ID: <CAG0CB23EHVaG54pjZiVt96rB8MX8T6zNMQ-RYurZdnsU2Vid0Q@mail.gmail.com>

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

From vladimir.fonov at gmail.com  Tue Apr  8 11:34:26 2014
From: vladimir.fonov at gmail.com (Vladimir S. FONOV)
Date: Tue, 08 Apr 2014 11:34:26 -0400
Subject: [MINC-development] Current release of MINC? New one needed I
 think...
In-Reply-To: <CAG0CB23EHVaG54pjZiVt96rB8MX8T6zNMQ-RYurZdnsU2Vid0Q@mail.gmail.com>
References: <20140403203813.435581257@mail.rogue-research.com>
	<CAG0CB23EHVaG54pjZiVt96rB8MX8T6zNMQ-RYurZdnsU2Vid0Q@mail.gmail.com>
Message-ID: <53441702.8050207@gmail.com>

Hello,

On 14-04-08 01:02 AM, Andrew Janke wrote:
> 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 think somebody should approach Alan Evans with this question.

-- 
Best regards,

  Vladimir S. FONOV ~ vladimir.fonov <at> gmail.com

From a.janke at gmail.com  Tue Apr  8 20:51:08 2014
From: a.janke at gmail.com (Andrew Janke)
Date: Wed, 9 Apr 2014 10:51:08 +1000
Subject: [MINC-development] Current release of MINC? New one needed I
	think...
In-Reply-To: <53441702.8050207@gmail.com>
References: <20140403203813.435581257@mail.rogue-research.com>
	<CAG0CB23EHVaG54pjZiVt96rB8MX8T6zNMQ-RYurZdnsU2Vid0Q@mail.gmail.com>
	<53441702.8050207@gmail.com>
Message-ID: <CAG0CB20Qpn3kprtf3esYWEKmUb2-ZLZKqNyGFYagrJSLr3kx_g@mail.gmail.com>

Hi Vladimir,

On 9 April 2014 01:34, Vladimir S. FONOV <vladimir.fonov at gmail.com> wrote:
> On 14-04-08 01:02 AM, Andrew Janke wrote:
>>
>> 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 think somebody should approach Alan Evans with this question.

Well I'm happy to do so but I'm not sure what the question is or the
answer you are seeking. Alan might be on this list in any case, I know
Louis was at one stage but given his email policy we might or might
not get a response!

In any case, MINC is now very much an international effort with people
submitting code and patches from all over. Granted there is still a
concentration of effort from Canada and more specifically Montreal
with yourself, Claude and others. Louis group has also been a strong
contributor but let's not forget the contributions of Jason, Steve,
John, Bert, Leila, Ilana, Simon, Peter and many others who's names
escape me now (sorry). Many of these people are now no longer BIC
specific.

Back on topic, I've been keen for a 2.2 release for some time, if you
can pull all the develop changes across to the main branch I'll update
all the Changelogs/NEWS and other documentation at which point others
can test and we'll release.

We should then put this release on packages.bic.mni.mcgill.ca or
perhaps given the github focus we should mirror all the old releases
from there and put them into github and leave a note there saying as
such. At that point Github would be the primary source of all things
minc including releases. Our current setup is:

   official releases: packages.bic.mni.mcgill.ca in .tar.gz
   source: github.com/BIC-MNI
   minc-toolkit:
www.bic.mni.mcgill.ca/ServicesSoftware/ServicesSoftwareMincToolKit
   Documentation: wikibooks

I can see an argument for killing packages.bic.mni.mcgill.ca others?

ta


a

From vladimir.fonov at gmail.com  Wed Apr  9 11:25:05 2014
From: vladimir.fonov at gmail.com (Vladimir S. FONOV)
Date: Wed, 09 Apr 2014 11:25:05 -0400
Subject: [MINC-development] Current release of MINC? New one needed I
 think...
In-Reply-To: <CAG0CB20Qpn3kprtf3esYWEKmUb2-ZLZKqNyGFYagrJSLr3kx_g@mail.gmail.com>
References: <20140403203813.435581257@mail.rogue-research.com>	<CAG0CB23EHVaG54pjZiVt96rB8MX8T6zNMQ-RYurZdnsU2Vid0Q@mail.gmail.com>	<53441702.8050207@gmail.com>
	<CAG0CB20Qpn3kprtf3esYWEKmUb2-ZLZKqNyGFYagrJSLr3kx_g@mail.gmail.com>
Message-ID: <53456651.1000706@gmail.com>

Hello,


I pushed the latest version into the master branch at 
https://github.com/BIC-MNI/libminc/ , but somebody should update 
https://github.com/BIC-MNI/libminc/blob/master/INSTALL.minc to replace 
autoconf/automake with cmake instructions.

On 14-04-08 08:51 PM, Andrew Janke wrote:
> Hi Vladimir,
>
> On 9 April 2014 01:34, Vladimir S. FONOV <vladimir.fonov at gmail.com> wrote:
>> On 14-04-08 01:02 AM, Andrew Janke wrote:
>>>
>>> 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 think somebody should approach Alan Evans with this question.
>
> Well I'm happy to do so but I'm not sure what the question is or the
> answer you are seeking. Alan might be on this list in any case, I know
> Louis was at one stage but given his email policy we might or might
> not get a response!
>
> In any case, MINC is now very much an international effort with people
> submitting code and patches from all over. Granted there is still a
> concentration of effort from Canada and more specifically Montreal
> with yourself, Claude and others. Louis group has also been a strong
> contributor but let's not forget the contributions of Jason, Steve,
> John, Bert, Leila, Ilana, Simon, Peter and many others who's names
> escape me now (sorry). Many of these people are now no longer BIC
> specific.
>
> Back on topic, I've been keen for a 2.2 release for some time, if you
> can pull all the develop changes across to the main branch I'll update
> all the Changelogs/NEWS and other documentation at which point others
> can test and we'll release.
>
> We should then put this release on packages.bic.mni.mcgill.ca or
> perhaps given the github focus we should mirror all the old releases
> from there and put them into github and leave a note there saying as
> such. At that point Github would be the primary source of all things
> minc including releases. Our current setup is:
>
>     official releases: packages.bic.mni.mcgill.ca in .tar.gz
>     source: github.com/BIC-MNI
>     minc-toolkit:
> www.bic.mni.mcgill.ca/ServicesSoftware/ServicesSoftwareMincToolKit
>     Documentation: wikibooks
>
> I can see an argument for killing packages.bic.mni.mcgill.ca others?
>
> ta
>
>
> a
> _______________________________________________
> MINC-development mailing list
> MINC-development at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
>


-- 
Best regards,

  Vladimir S. FONOV ~ vladimir.fonov <at> gmail.com

From matthijs at mouseimaging.ca  Wed Apr  9 15:59:22 2014
From: matthijs at mouseimaging.ca (Matthijs van Eede)
Date: Wed, 9 Apr 2014 15:59:22 -0400 (EDT)
Subject: [MINC-development] Current release of MINC? New one needed
	I	think...
In-Reply-To: <CAG0CB23EHVaG54pjZiVt96rB8MX8T6zNMQ-RYurZdnsU2Vid0Q@mail.gmail.com>
References: <20140403203813.435581257@mail.rogue-research.com>
	<CAG0CB23EHVaG54pjZiVt96rB8MX8T6zNMQ-RYurZdnsU2Vid0Q@mail.gmail.com>
Message-ID: <1910846751.2294165.1397073562881.JavaMail.root@mouseimaging.ca>

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

From a.janke at gmail.com  Fri Apr 11 08:44:14 2014
From: a.janke at gmail.com (Andrew Janke)
Date: Fri, 11 Apr 2014 22:44:14 +1000
Subject: [MINC-development] Current release of MINC? New one needed I
	think...
In-Reply-To: <1910846751.2294165.1397073562881.JavaMail.root@mouseimaging.ca>
References: <20140403203813.435581257@mail.rogue-research.com>
	<CAG0CB23EHVaG54pjZiVt96rB8MX8T6zNMQ-RYurZdnsU2Vid0Q@mail.gmail.com>
	<1910846751.2294165.1397073562881.JavaMail.root@mouseimaging.ca>
Message-ID: <CAG0CB202T8VPyPDqfhMH7QGsYd18tY5xQKcJPjVpAC5qy7byLg@mail.gmail.com>

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

From vladimir.fonov at gmail.com  Fri Apr 11 09:49:43 2014
From: vladimir.fonov at gmail.com (Vladimir S. FONOV)
Date: Fri, 11 Apr 2014 09:49:43 -0400
Subject: [MINC-development] Current release of MINC? New one needed I
	think...
In-Reply-To: <CAG0CB202T8VPyPDqfhMH7QGsYd18tY5xQKcJPjVpAC5qy7byLg@mail.gmail.com>
References: <20140403203813.435581257@mail.rogue-research.com>
	<CAG0CB23EHVaG54pjZiVt96rB8MX8T6zNMQ-RYurZdnsU2Vid0Q@mail.gmail.com>
	<1910846751.2294165.1397073562881.JavaMail.root@mouseimaging.ca>
	<CAG0CB202T8VPyPDqfhMH7QGsYd18tY5xQKcJPjVpAC5qy7byLg@mail.gmail.com>
Message-ID: <D681A325-73F0-4E84-858E-6F067DDF41FA@gmail.com>

Hello  Matthijs,

I added you in the list of contributors on github, so now you can commit to the repositories directly . 




On Apr 11, 2014, at 8:44 AM, Andrew Janke <a.janke at gmail.com> wrote:

> 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
> _______________________________________________
> MINC-development mailing list
> MINC-development at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development

---
Best regards,

Vladimir S. FONOV ~ v.s.fonov <at> ilmarin.info






From a.janke at gmail.com  Fri Apr 11 11:25:58 2014
From: a.janke at gmail.com (Andrew Janke)
Date: Sat, 12 Apr 2014 01:25:58 +1000
Subject: [MINC-development] Current release of MINC? New one needed I
	think...
In-Reply-To: <CAG0CB202T8VPyPDqfhMH7QGsYd18tY5xQKcJPjVpAC5qy7byLg@mail.gmail.com>
References: <20140403203813.435581257@mail.rogue-research.com>
	<CAG0CB23EHVaG54pjZiVt96rB8MX8T6zNMQ-RYurZdnsU2Vid0Q@mail.gmail.com>
	<1910846751.2294165.1397073562881.JavaMail.root@mouseimaging.ca>
	<CAG0CB202T8VPyPDqfhMH7QGsYd18tY5xQKcJPjVpAC5qy7byLg@mail.gmail.com>
Message-ID: <CAG0CB20Fom2v+J-CFP2-ytM8v1NyKk9+KuWM0eaoPdopuMH2Uw@mail.gmail.com>

OK, here goes.

I have updated README.release with the process to follow in libminc,
Vladimir may have some comment here specific to the cmake style of
packaging things.

   https://github.com/BIC-MNI/libminc/blob/develop/README.release

minc-tools will be very similar, it is still unclear how the release
of libminc and minc-tools will coincide. One for yourself and Vlad to
work through, perhaps the easiest for now is to make them happen at
the same time with differing version numbers.

You will note that we use a ChangeLog in libminc and minc-tools, the
idea is that each developer summarises their changes in this for other
developers to understand what is going on without having to trawl
through commit logs. Perhaps this notion is now outdated with github
but I still find it useful.

Before a release it is now your job to update the NEWS file from the
ChangeLog, a different style of writing is needed in here as these
describe the changes that were made for the users rather than a
programmers benefit. If you look back though the history you will get
an idea of what needs to be done.

I make it a habit to check through all the documentation before
releasing. In order that upstream packagers can build easily, all
binaries require at a minimum a skeleton manual page. There are
examples in minc-tools of how to do this for scripts (perl and sh) and
C code

Once this is all done, update the various version numbers, release,
test build, run your test cases and put up an initial .tar.gz on
minc-dev for a few of us to test. If no bugs are found within 2-3
weeks I then release the package via an announcement on minc-users and
copy it to packages.bic.mni.mcgill.ca My suggestion would be to retire
this as a place to put .tar.gz files and instead use the github
releases mechanism.

What is then done with packages.bic.mni.mcill.ca after all these years
is another matter!.

Let me know if you need any help and from all of us, thanks for
volunteering your time and effort.

ta


a




On 11 April 2014 22:44, Andrew Janke <a.janke at gmail.com> wrote:
> 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

From vladimir.fonov at gmail.com  Fri Apr 11 11:41:22 2014
From: vladimir.fonov at gmail.com (Vladimir S. FONOV)
Date: Fri, 11 Apr 2014 11:41:22 -0400
Subject: [MINC-development] Current release of MINC? New one needed I
	think...
In-Reply-To: <CAG0CB20Fom2v+J-CFP2-ytM8v1NyKk9+KuWM0eaoPdopuMH2Uw@mail.gmail.com>
References: <20140403203813.435581257@mail.rogue-research.com>
	<CAG0CB23EHVaG54pjZiVt96rB8MX8T6zNMQ-RYurZdnsU2Vid0Q@mail.gmail.com>
	<1910846751.2294165.1397073562881.JavaMail.root@mouseimaging.ca>
	<CAG0CB202T8VPyPDqfhMH7QGsYd18tY5xQKcJPjVpAC5qy7byLg@mail.gmail.com>
	<CAG0CB20Fom2v+J-CFP2-ytM8v1NyKk9+KuWM0eaoPdopuMH2Uw@mail.gmail.com>
Message-ID: <CAMCwi7M_t+C0Kb5MoEdmNhKLWS3=JOT872=qUESepN0vAR6DuQ@mail.gmail.com>

Maybe it's worth to ditch the man pages and perldoc pages and transfer
everything to wikibooks ?
Or at least convert man syntax to markup syntax?

On Fri, Apr 11, 2014 at 11:25 AM, Andrew Janke <a.janke at gmail.com> wrote:
> OK, here goes.
>
> I have updated README.release with the process to follow in libminc,
> Vladimir may have some comment here specific to the cmake style of
> packaging things.
>
>    https://github.com/BIC-MNI/libminc/blob/develop/README.release
>
> minc-tools will be very similar, it is still unclear how the release
> of libminc and minc-tools will coincide. One for yourself and Vlad to
> work through, perhaps the easiest for now is to make them happen at
> the same time with differing version numbers.
>
> You will note that we use a ChangeLog in libminc and minc-tools, the
> idea is that each developer summarises their changes in this for other
> developers to understand what is going on without having to trawl
> through commit logs. Perhaps this notion is now outdated with github
> but I still find it useful.
>
> Before a release it is now your job to update the NEWS file from the
> ChangeLog, a different style of writing is needed in here as these
> describe the changes that were made for the users rather than a
> programmers benefit. If you look back though the history you will get
> an idea of what needs to be done.
>
> I make it a habit to check through all the documentation before
> releasing. In order that upstream packagers can build easily, all
> binaries require at a minimum a skeleton manual page. There are
> examples in minc-tools of how to do this for scripts (perl and sh) and
> C code
>
> Once this is all done, update the various version numbers, release,
> test build, run your test cases and put up an initial .tar.gz on
> minc-dev for a few of us to test. If no bugs are found within 2-3
> weeks I then release the package via an announcement on minc-users and
> copy it to packages.bic.mni.mcgill.ca My suggestion would be to retire
> this as a place to put .tar.gz files and instead use the github
> releases mechanism.
>
> What is then done with packages.bic.mni.mcill.ca after all these years
> is another matter!.
>
> Let me know if you need any help and from all of us, thanks for
> volunteering your time and effort.
>
> ta
>
>
> a
>
>
>
>
> On 11 April 2014 22:44, Andrew Janke <a.janke at gmail.com> wrote:
>> 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
> _______________________________________________
> MINC-development mailing list
> MINC-development at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development



-- 
Best regards,

 Vladimir S. Fonov ~ vladimir <dot> fonov <at> gmail <dot> com

From a.janke at gmail.com  Fri Apr 11 11:44:21 2014
From: a.janke at gmail.com (Andrew Janke)
Date: Sat, 12 Apr 2014 01:44:21 +1000
Subject: [MINC-development] Current release of MINC? New one needed I
	think...
In-Reply-To: <CAMCwi7M_t+C0Kb5MoEdmNhKLWS3=JOT872=qUESepN0vAR6DuQ@mail.gmail.com>
References: <20140403203813.435581257@mail.rogue-research.com>
	<CAG0CB23EHVaG54pjZiVt96rB8MX8T6zNMQ-RYurZdnsU2Vid0Q@mail.gmail.com>
	<1910846751.2294165.1397073562881.JavaMail.root@mouseimaging.ca>
	<CAG0CB202T8VPyPDqfhMH7QGsYd18tY5xQKcJPjVpAC5qy7byLg@mail.gmail.com>
	<CAG0CB20Fom2v+J-CFP2-ytM8v1NyKk9+KuWM0eaoPdopuMH2Uw@mail.gmail.com>
	<CAMCwi7M_t+C0Kb5MoEdmNhKLWS3=JOT872=qUESepN0vAR6DuQ@mail.gmail.com>
Message-ID: <CAG0CB22TjT20U7BYHgk9Zixy=gBMdKyVATKG730jUa24MpVndQ@mail.gmail.com>

On 12 April 2014 01:41, Vladimir S. FONOV <vladimir.fonov at gmail.com> wrote:
> Maybe it's worth to ditch the man pages and perldoc pages and transfer
> everything to wikibooks ?
> Or at least convert man syntax to markup syntax?

This would make sense if there is a way to convert these (in .md
syntax?) to something that can be a manual page for builds on
debian/Ubuntu. Most distributions require a man page for executables.

So if there is a way I'm all for it!


a

From a.janke at gmail.com  Sun Apr 13 11:23:50 2014
From: a.janke at gmail.com (Andrew Janke)
Date: Mon, 14 Apr 2014 01:23:50 +1000
Subject: [MINC-development] Current release of MINC? New one needed I
	think...
In-Reply-To: <53456651.1000706@gmail.com>
References: <20140403203813.435581257@mail.rogue-research.com>
	<CAG0CB23EHVaG54pjZiVt96rB8MX8T6zNMQ-RYurZdnsU2Vid0Q@mail.gmail.com>
	<53441702.8050207@gmail.com>
	<CAG0CB20Qpn3kprtf3esYWEKmUb2-ZLZKqNyGFYagrJSLr3kx_g@mail.gmail.com>
	<53456651.1000706@gmail.com>
Message-ID: <CAG0CB21OWwrjWZsh1_mj3SWY55SL8x5F89CZmhT9Vq_6gn2UDg@mail.gmail.com>

On 10 April 2014 01:25, Vladimir S. FONOV <vladimir.fonov at gmail.com> wrote:
> I pushed the latest version into the master branch at
> https://github.com/BIC-MNI/libminc/ , but somebody should update
> https://github.com/BIC-MNI/libminc/blob/master/INSTALL.minc to replace
> autoconf/automake with cmake instructions.

Hi Vlad,

Thanks for this, I'll pull the changes down, build and test it here.
You'll note I
made this for INSTALL.minc (and renamed it INSTALL).

   https://github.com/BIC-MNI/libminc/issues/17

I'd appreciate it if you add some bare bones instructions given you
are the official MINC cmake guru, I am guessing you will recommend an
out of course build. It's what I do with cmake but don't know if this
is still the cool and hip way of doing things with cmake.

I'll add all the flowery explanatory text around it if you just want
to add a series of command lines that need to be run.



a