All, There will very likely be a 1.3.2 release (and possibly more in the 1.3.x series) given that 1.4 has many planned features and is almost an year away. So, whenever you commit any bug fixes to trunk, remember that it is your responsibility to merge them into the 1.3.x branch -- do not wait for someone else to do the merge for you. Features that change ABI compatibility (such as adding MPI-3 features) should not go into 1.3.x. I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional. Bill: r7447 looks like a bug-fix. Can you merge it into the 1.3.x branch? Dave: r7462 adds the qsort capability to Comm_split. Can you merge it into the 1.3.x branch? Thanks, -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji
I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional.
These will be merged soon. I was waiting for the 1.3.1 release. -Jayesh ----- Original Message ----- From: Pavan Balaji <[email protected]> To: [email protected] Cc: William Gropp <[email protected]> Sent: Fri, 19 Nov 2010 15:21:01 -0600 (CST) Subject: [mpich2-core] Merges into the 1.3.x branch All, There will very likely be a 1.3.2 release (and possibly more in the 1.3.x series) given that 1.4 has many planned features and is almost an year away. So, whenever you commit any bug fixes to trunk, remember that it is your responsibility to merge them into the 1.3.x branch -- do not wait for someone else to do the merge for you. Features that change ABI compatibility (such as adding MPI-3 features) should not go into 1.3.x. I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional. Bill: r7447 looks like a bug-fix. Can you merge it into the 1.3.x branch? Dave: r7462 adds the qsort capability to Comm_split. Can you merge it into the 1.3.x branch? Thanks, -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji
Reminder to Jayesh and Bill. This will take < 5 minutes to do. I'm intentionally avoiding doing this myself, as this is everyone's responsibility. -- Pavan On 11/19/2010 03:43 PM, Jayesh Krishna wrote:
I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional.
These will be merged soon. I was waiting for the 1.3.1 release.
-Jayesh ----- Original Message ----- From: Pavan Balaji<[email protected]> To: [email protected] Cc: William Gropp<[email protected]> Sent: Fri, 19 Nov 2010 15:21:01 -0600 (CST) Subject: [mpich2-core] Merges into the 1.3.x branch
All,
There will very likely be a 1.3.2 release (and possibly more in the 1.3.x series) given that 1.4 has many planned features and is almost an year away.
So, whenever you commit any bug fixes to trunk, remember that it is your responsibility to merge them into the 1.3.x branch -- do not wait for someone else to do the merge for you. Features that change ABI compatibility (such as adding MPI-3 features) should not go into 1.3.x.
I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional.
Bill: r7447 looks like a bug-fix. Can you merge it into the 1.3.x branch?
Dave: r7462 adds the qsort capability to Comm_split. Can you merge it into the 1.3.x branch?
Thanks,
-- Pavan
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
I don't think you have to do the merging for my changes. It is in my "to do" list - no reminder required. -Jayesh ----- Original Message ----- From: Pavan Balaji <[email protected]> To: [email protected] Cc: Jayesh Krishna <[email protected]>, William Gropp <[email protected]> Sent: Tue, 23 Nov 2010 02:32:33 -0600 (CST) Subject: Re: [mpich2-core] Merges into the 1.3.x branch Reminder to Jayesh and Bill. This will take < 5 minutes to do. I'm intentionally avoiding doing this myself, as this is everyone's responsibility. -- Pavan On 11/19/2010 03:43 PM, Jayesh Krishna wrote:
I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional.
These will be merged soon. I was waiting for the 1.3.1 release.
-Jayesh ----- Original Message ----- From: Pavan Balaji<[email protected]> To: [email protected] Cc: William Gropp<[email protected]> Sent: Fri, 19 Nov 2010 15:21:01 -0600 (CST) Subject: [mpich2-core] Merges into the 1.3.x branch
All,
There will very likely be a 1.3.2 release (and possibly more in the 1.3.x series) given that 1.4 has many planned features and is almost an year away.
So, whenever you commit any bug fixes to trunk, remember that it is your responsibility to merge them into the 1.3.x branch -- do not wait for someone else to do the merge for you. Features that change ABI compatibility (such as adding MPI-3 features) should not go into 1.3.x.
I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional.
Bill: r7447 looks like a bug-fix. Can you merge it into the 1.3.x branch?
Dave: r7462 adds the qsort capability to Comm_split. Can you merge it into the 1.3.x branch?
Thanks,
-- Pavan
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
On 11/23/2010 03:47 AM, Jayesh Krishna wrote:
I don't think you have to do the merging for my changes. It is in my "to do" list - no reminder required.
I'm not going to merge your changes. The earlier you merge, the longer time it has to go through the nightly tests and catch any issues that might have crept in. I'm curious to know what the hold up is. If everyone gets into the habit of merging changes to the appropriate branches on time, the rest of us don't have to worry about whether all commits made it in or not. In one of the previous releases, Dave and I spent a lot of time figuring out what all commits were merged into a release branch and what weren't, which could have easily been avoided if everyone was disciplined enough to merge their changes in as soon as they committed to trunk. -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji
the rest of us don't have to worry ... don't worry be happy... :)
I spent a lot of time figuring out what all commits were merged ... you won't have to do that for my changes...
everyone was disciplined ... mpich2 team is full of spoilt brats ...:)
-Jayesh ----- Original Message ----- From: Pavan Balaji <[email protected]> To: Jayesh Krishna <[email protected]> Cc: [email protected], William Gropp <[email protected]> Sent: Tue, 23 Nov 2010 07:27:22 -0600 (CST) Subject: Re: [mpich2-core] Merges into the 1.3.x branch On 11/23/2010 03:47 AM, Jayesh Krishna wrote:
I don't think you have to do the merging for my changes. It is in my "to do" list - no reminder required.
I'm not going to merge your changes. The earlier you merge, the longer time it has to go through the nightly tests and catch any issues that might have crept in. I'm curious to know what the hold up is. If everyone gets into the habit of merging changes to the appropriate branches on time, the rest of us don't have to worry about whether all commits made it in or not. In one of the previous releases, Dave and I spent a lot of time figuring out what all commits were merged into a release branch and what weren't, which could have easily been avoided if everyone was disciplined enough to merge their changes in as soon as they committed to trunk. -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji
Pavan, This is the first that I've heard of the 1.3.x branch - I don't even know how to do this for svn (I did know how to do it for cvs). Is this on the wiki? I looked at http://wiki.mcs.anl.gov/mpich2/index.php/Creating_a_Release , but that suggests that a release is created from the trunk and not updated after that (except for critical fixes in the release), which is why I've tried to get things into the trunk as soon as possible. Anyway, if you can tell me what svn commands to use and what fixes you'd like me to add, I'll be happy to do it. (I'll put in a plea to remember that it is also everyone's responsibility to keep the documentation, both on the release process and the design documents, up to date - that discipline will save a tremendous amount of time for everyone else.) Bill On Nov 19, 2010, at 3:21 PM, Pavan Balaji wrote:
All,
There will very likely be a 1.3.2 release (and possibly more in the 1.3.x series) given that 1.4 has many planned features and is almost an year away.
So, whenever you commit any bug fixes to trunk, remember that it is your responsibility to merge them into the 1.3.x branch -- do not wait for someone else to do the merge for you. Features that change ABI compatibility (such as adding MPI-3 features) should not go into 1.3.x.
I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional.
Bill: r7447 looks like a bug-fix. Can you merge it into the 1.3.x branch?
Dave: r7462 adds the qsort capability to Comm_split. Can you merge it into the 1.3.x branch?
Thanks,
-- Pavan
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
Bill, I have already merged r7447 from trunk to 1.3.x, but it can be done as follows: % check out 1.3.x branch % cd into it % svn merge -c 7447 url-of-trunk . % commit That's it. Also, in case you are filtering mpich2-core into a read-occasionally folder, such mails (about 1.3.x) get sent there. Pavan also CCed you explicitly on some mails, but the mailer may not send it separately if you are already included in the list (at least some times it happens that way). Rajeev On Nov 30, 2010, at 10:01 AM, William Gropp wrote:
Pavan,
This is the first that I've heard of the 1.3.x branch - I don't even know how to do this for svn (I did know how to do it for cvs).
Is this on the wiki? I looked at http://wiki.mcs.anl.gov/mpich2/index.php/Creating_a_Release , but that suggests that a release is created from the trunk and not updated after that (except for critical fixes in the release), which is why I've tried to get things into the trunk as soon as possible.
Anyway, if you can tell me what svn commands to use and what fixes you'd like me to add, I'll be happy to do it.
(I'll put in a plea to remember that it is also everyone's responsibility to keep the documentation, both on the release process and the design documents, up to date - that discipline will save a tremendous amount of time for everyone else.)
Bill
On Nov 19, 2010, at 3:21 PM, Pavan Balaji wrote:
All,
There will very likely be a 1.3.2 release (and possibly more in the 1.3.x series) given that 1.4 has many planned features and is almost an year away.
So, whenever you commit any bug fixes to trunk, remember that it is your responsibility to merge them into the 1.3.x branch -- do not wait for someone else to do the merge for you. Features that change ABI compatibility (such as adding MPI-3 features) should not go into 1.3.x.
I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional.
Bill: r7447 looks like a bug-fix. Can you merge it into the 1.3.x branch?
Dave: r7462 adds the qsort capability to Comm_split. Can you merge it into the 1.3.x branch?
Thanks,
-- Pavan
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
Thanks - I do filter mpich2-core, so cc'ing me doesn't help (that would be a useful mailer feature - overriding the filter for a list when explicitly included). I've add this to the release page since I have it handy. Bill On Nov 30, 2010, at 10:25 AM, Rajeev Thakur wrote:
Bill, I have already merged r7447 from trunk to 1.3.x, but it can be done as follows:
% check out 1.3.x branch % cd into it % svn merge -c 7447 url-of-trunk . % commit
That's it.
Also, in case you are filtering mpich2-core into a read-occasionally folder, such mails (about 1.3.x) get sent there. Pavan also CCed you explicitly on some mails, but the mailer may not send it separately if you are already included in the list (at least some times it happens that way).
Rajeev
On Nov 30, 2010, at 10:01 AM, William Gropp wrote:
Pavan,
This is the first that I've heard of the 1.3.x branch - I don't even know how to do this for svn (I did know how to do it for cvs).
Is this on the wiki? I looked at http://wiki.mcs.anl.gov/mpich2/index.php/Creating_a_Release , but that suggests that a release is created from the trunk and not updated after that (except for critical fixes in the release), which is why I've tried to get things into the trunk as soon as possible.
Anyway, if you can tell me what svn commands to use and what fixes you'd like me to add, I'll be happy to do it.
(I'll put in a plea to remember that it is also everyone's responsibility to keep the documentation, both on the release process and the design documents, up to date - that discipline will save a tremendous amount of time for everyone else.)
Bill
On Nov 19, 2010, at 3:21 PM, Pavan Balaji wrote:
All,
There will very likely be a 1.3.2 release (and possibly more in the 1.3.x series) given that 1.4 has many planned features and is almost an year away.
So, whenever you commit any bug fixes to trunk, remember that it is your responsibility to merge them into the 1.3.x branch -- do not wait for someone else to do the merge for you. Features that change ABI compatibility (such as adding MPI-3 features) should not go into 1.3.x.
I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional.
Bill: r7447 looks like a bug-fix. Can you merge it into the 1.3.x branch?
Dave: r7462 adds the qsort capability to Comm_split. Can you merge it into the 1.3.x branch?
Thanks,
-- Pavan
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
Would it make sense to have a wiki page on the status of a release, including any outstanding bugs and whether it is still open for updates? I know we have email for this, but in looking over my email, I'm uncertain as to the status or even the value of x. Bill On Nov 30, 2010, at 11:32 AM, William Gropp wrote:
Thanks - I do filter mpich2-core, so cc'ing me doesn't help (that would be a useful mailer feature - overriding the filter for a list when explicitly included).
I've add this to the release page since I have it handy.
Bill
On Nov 30, 2010, at 10:25 AM, Rajeev Thakur wrote:
Bill, I have already merged r7447 from trunk to 1.3.x, but it can be done as follows:
% check out 1.3.x branch % cd into it % svn merge -c 7447 url-of-trunk . % commit
That's it.
Also, in case you are filtering mpich2-core into a read-occasionally folder, such mails (about 1.3.x) get sent there. Pavan also CCed you explicitly on some mails, but the mailer may not send it separately if you are already included in the list (at least some times it happens that way).
Rajeev
On Nov 30, 2010, at 10:01 AM, William Gropp wrote:
Pavan,
This is the first that I've heard of the 1.3.x branch - I don't even know how to do this for svn (I did know how to do it for cvs).
Is this on the wiki? I looked at http://wiki.mcs.anl.gov/mpich2/index.php/Creating_a_Release , but that suggests that a release is created from the trunk and not updated after that (except for critical fixes in the release), which is why I've tried to get things into the trunk as soon as possible.
Anyway, if you can tell me what svn commands to use and what fixes you'd like me to add, I'll be happy to do it.
(I'll put in a plea to remember that it is also everyone's responsibility to keep the documentation, both on the release process and the design documents, up to date - that discipline will save a tremendous amount of time for everyone else.)
Bill
On Nov 19, 2010, at 3:21 PM, Pavan Balaji wrote:
All,
There will very likely be a 1.3.2 release (and possibly more in the 1.3.x series) given that 1.4 has many planned features and is almost an year away.
So, whenever you commit any bug fixes to trunk, remember that it is your responsibility to merge them into the 1.3.x branch -- do not wait for someone else to do the merge for you. Features that change ABI compatibility (such as adding MPI-3 features) should not go into 1.3.x.
I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional.
Bill: r7447 looks like a bug-fix. Can you merge it into the 1.3.x branch?
Dave: r7462 adds the qsort capability to Comm_split. Can you merge it into the 1.3.x branch?
Thanks,
-- Pavan
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
Like this? https://trac.mcs.anl.gov/projects/mpich2/roadmap https://trac.mcs.anl.gov/projects/mpich2/milestone/mpich2-1.3.2 -Dave On Nov 30, 2010, at 1:38 PM CST, William Gropp wrote:
Would it make sense to have a wiki page on the status of a release, including any outstanding bugs and whether it is still open for updates? I know we have email for this, but in looking over my email, I'm uncertain as to the status or even the value of x.
Bill
On Nov 30, 2010, at 11:32 AM, William Gropp wrote:
Thanks - I do filter mpich2-core, so cc'ing me doesn't help (that would be a useful mailer feature - overriding the filter for a list when explicitly included).
I've add this to the release page since I have it handy.
Bill
On Nov 30, 2010, at 10:25 AM, Rajeev Thakur wrote:
Bill, I have already merged r7447 from trunk to 1.3.x, but it can be done as follows:
% check out 1.3.x branch % cd into it % svn merge -c 7447 url-of-trunk . % commit
That's it.
Also, in case you are filtering mpich2-core into a read-occasionally folder, such mails (about 1.3.x) get sent there. Pavan also CCed you explicitly on some mails, but the mailer may not send it separately if you are already included in the list (at least some times it happens that way).
Rajeev
On Nov 30, 2010, at 10:01 AM, William Gropp wrote:
Pavan,
This is the first that I've heard of the 1.3.x branch - I don't even know how to do this for svn (I did know how to do it for cvs).
Is this on the wiki? I looked at http://wiki.mcs.anl.gov/mpich2/index.php/Creating_a_Release , but that suggests that a release is created from the trunk and not updated after that (except for critical fixes in the release), which is why I've tried to get things into the trunk as soon as possible.
Anyway, if you can tell me what svn commands to use and what fixes you'd like me to add, I'll be happy to do it.
(I'll put in a plea to remember that it is also everyone's responsibility to keep the documentation, both on the release process and the design documents, up to date - that discipline will save a tremendous amount of time for everyone else.)
Bill
On Nov 19, 2010, at 3:21 PM, Pavan Balaji wrote:
All,
There will very likely be a 1.3.2 release (and possibly more in the 1.3.x series) given that 1.4 has many planned features and is almost an year away.
So, whenever you commit any bug fixes to trunk, remember that it is your responsibility to merge them into the 1.3.x branch -- do not wait for someone else to do the merge for you. Features that change ABI compatibility (such as adding MPI-3 features) should not go into 1.3.x.
I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional.
Bill: r7447 looks like a bug-fix. Can you merge it into the 1.3.x branch?
Dave: r7462 adds the qsort capability to Comm_split. Can you merge it into the 1.3.x branch?
Thanks,
-- Pavan
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
Thanks! I'll update the release wiki page to point to these. One question - I tried to follow the directions that Rajeev sent, and I was able to checkout a 1.3.1 release branch but not a 1.3.2 branch. I take it this means that the value of x is 1? Bill On Nov 30, 2010, at 2:15 PM, Dave Goodell wrote:
Like this?
https://trac.mcs.anl.gov/projects/mpich2/roadmap https://trac.mcs.anl.gov/projects/mpich2/milestone/mpich2-1.3.2
-Dave
On Nov 30, 2010, at 1:38 PM CST, William Gropp wrote:
Would it make sense to have a wiki page on the status of a release, including any outstanding bugs and whether it is still open for updates? I know we have email for this, but in looking over my email, I'm uncertain as to the status or even the value of x.
Bill
On Nov 30, 2010, at 11:32 AM, William Gropp wrote:
Thanks - I do filter mpich2-core, so cc'ing me doesn't help (that would be a useful mailer feature - overriding the filter for a list when explicitly included).
I've add this to the release page since I have it handy.
Bill
On Nov 30, 2010, at 10:25 AM, Rajeev Thakur wrote:
Bill, I have already merged r7447 from trunk to 1.3.x, but it can be done as follows:
% check out 1.3.x branch % cd into it % svn merge -c 7447 url-of-trunk . % commit
That's it.
Also, in case you are filtering mpich2-core into a read- occasionally folder, such mails (about 1.3.x) get sent there. Pavan also CCed you explicitly on some mails, but the mailer may not send it separately if you are already included in the list (at least some times it happens that way).
Rajeev
On Nov 30, 2010, at 10:01 AM, William Gropp wrote:
Pavan,
This is the first that I've heard of the 1.3.x branch - I don't even know how to do this for svn (I did know how to do it for cvs).
Is this on the wiki? I looked at http://wiki.mcs.anl.gov/mpich2/index.php/Creating_a_Release , but that suggests that a release is created from the trunk and not updated after that (except for critical fixes in the release), which is why I've tried to get things into the trunk as soon as possible.
Anyway, if you can tell me what svn commands to use and what fixes you'd like me to add, I'll be happy to do it.
(I'll put in a plea to remember that it is also everyone's responsibility to keep the documentation, both on the release process and the design documents, up to date - that discipline will save a tremendous amount of time for everyone else.)
Bill
On Nov 19, 2010, at 3:21 PM, Pavan Balaji wrote:
All,
There will very likely be a 1.3.2 release (and possibly more in the 1.3.x series) given that 1.4 has many planned features and is almost an year away.
So, whenever you commit any bug fixes to trunk, remember that it is your responsibility to merge them into the 1.3.x branch -- do not wait for someone else to do the merge for you. Features that change ABI compatibility (such as adding MPI-3 features) should not go into 1.3.x.
I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional.
Bill: r7447 looks like a bug-fix. Can you merge it into the 1.3.x branch?
Dave: r7462 adds the qsort capability to Comm_split. Can you merge it into the 1.3.x branch?
Thanks,
-- Pavan
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
There is a branch called 1.3.x. Rajeev On Nov 30, 2010, at 7:30 PM, William Gropp wrote:
Thanks! I'll update the release wiki page to point to these.
One question - I tried to follow the directions that Rajeev sent, and I was able to checkout a 1.3.1 release branch but not a 1.3.2 branch. I take it this means that the value of x is 1?
Bill
On Nov 30, 2010, at 2:15 PM, Dave Goodell wrote:
Like this?
https://trac.mcs.anl.gov/projects/mpich2/roadmap https://trac.mcs.anl.gov/projects/mpich2/milestone/mpich2-1.3.2
-Dave
On Nov 30, 2010, at 1:38 PM CST, William Gropp wrote:
Would it make sense to have a wiki page on the status of a release, including any outstanding bugs and whether it is still open for updates? I know we have email for this, but in looking over my email, I'm uncertain as to the status or even the value of x.
Bill
On Nov 30, 2010, at 11:32 AM, William Gropp wrote:
Thanks - I do filter mpich2-core, so cc'ing me doesn't help (that would be a useful mailer feature - overriding the filter for a list when explicitly included).
I've add this to the release page since I have it handy.
Bill
On Nov 30, 2010, at 10:25 AM, Rajeev Thakur wrote:
Bill, I have already merged r7447 from trunk to 1.3.x, but it can be done as follows:
% check out 1.3.x branch % cd into it % svn merge -c 7447 url-of-trunk . % commit
That's it.
Also, in case you are filtering mpich2-core into a read-occasionally folder, such mails (about 1.3.x) get sent there. Pavan also CCed you explicitly on some mails, but the mailer may not send it separately if you are already included in the list (at least some times it happens that way).
Rajeev
On Nov 30, 2010, at 10:01 AM, William Gropp wrote:
Pavan,
This is the first that I've heard of the 1.3.x branch - I don't even know how to do this for svn (I did know how to do it for cvs).
Is this on the wiki? I looked at http://wiki.mcs.anl.gov/mpich2/index.php/Creating_a_Release , but that suggests that a release is created from the trunk and not updated after that (except for critical fixes in the release), which is why I've tried to get things into the trunk as soon as possible.
Anyway, if you can tell me what svn commands to use and what fixes you'd like me to add, I'll be happy to do it.
(I'll put in a plea to remember that it is also everyone's responsibility to keep the documentation, both on the release process and the design documents, up to date - that discipline will save a tremendous amount of time for everyone else.)
Bill
On Nov 19, 2010, at 3:21 PM, Pavan Balaji wrote:
All,
There will very likely be a 1.3.2 release (and possibly more in the 1.3.x series) given that 1.4 has many planned features and is almost an year away.
So, whenever you commit any bug fixes to trunk, remember that it is your responsibility to merge them into the 1.3.x branch -- do not wait for someone else to do the merge for you. Features that change ABI compatibility (such as adding MPI-3 features) should not go into 1.3.x.
I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional.
Bill: r7447 looks like a bug-fix. Can you merge it into the 1.3.x branch?
Dave: r7462 adds the qsort capability to Comm_split. Can you merge it into the 1.3.x branch?
Thanks,
-- Pavan
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
One more clarification -- all commits that do not change the ABI string for 1.3.x should go into the 1.3.x branch as well. So far, this includes all commits, except the non-blocking collectives related commits. So if you haven't merged something into 1.3.x yet, please do so. Thanks, -- Pavan On 11/30/2010 07:35 PM, Rajeev Thakur wrote:
There is a branch called 1.3.x.
Rajeev
On Nov 30, 2010, at 7:30 PM, William Gropp wrote:
Thanks! I'll update the release wiki page to point to these.
One question - I tried to follow the directions that Rajeev sent, and I was able to checkout a 1.3.1 release branch but not a 1.3.2 branch. I take it this means that the value of x is 1?
Bill
On Nov 30, 2010, at 2:15 PM, Dave Goodell wrote:
Like this?
https://trac.mcs.anl.gov/projects/mpich2/roadmap https://trac.mcs.anl.gov/projects/mpich2/milestone/mpich2-1.3.2
-Dave
On Nov 30, 2010, at 1:38 PM CST, William Gropp wrote:
Would it make sense to have a wiki page on the status of a release, including any outstanding bugs and whether it is still open for updates? I know we have email for this, but in looking over my email, I'm uncertain as to the status or even the value of x.
Bill
On Nov 30, 2010, at 11:32 AM, William Gropp wrote:
Thanks - I do filter mpich2-core, so cc'ing me doesn't help (that would be a useful mailer feature - overriding the filter for a list when explicitly included).
I've add this to the release page since I have it handy.
Bill
On Nov 30, 2010, at 10:25 AM, Rajeev Thakur wrote:
Bill, I have already merged r7447 from trunk to 1.3.x, but it can be done as follows:
% check out 1.3.x branch % cd into it % svn merge -c 7447 url-of-trunk . % commit
That's it.
Also, in case you are filtering mpich2-core into a read-occasionally folder, such mails (about 1.3.x) get sent there. Pavan also CCed you explicitly on some mails, but the mailer may not send it separately if you are already included in the list (at least some times it happens that way).
Rajeev
On Nov 30, 2010, at 10:01 AM, William Gropp wrote:
Pavan,
This is the first that I've heard of the 1.3.x branch - I don't even know how to do this for svn (I did know how to do it for cvs).
Is this on the wiki? I looked at http://wiki.mcs.anl.gov/mpich2/index.php/Creating_a_Release , but that suggests that a release is created from the trunk and not updated after that (except for critical fixes in the release), which is why I've tried to get things into the trunk as soon as possible.
Anyway, if you can tell me what svn commands to use and what fixes you'd like me to add, I'll be happy to do it.
(I'll put in a plea to remember that it is also everyone's responsibility to keep the documentation, both on the release process and the design documents, up to date - that discipline will save a tremendous amount of time for everyone else.)
Bill
On Nov 19, 2010, at 3:21 PM, Pavan Balaji wrote:
All,
There will very likely be a 1.3.2 release (and possibly more in the 1.3.x series) given that 1.4 has many planned features and is almost an year away.
So, whenever you commit any bug fixes to trunk, remember that it is your responsibility to merge them into the 1.3.x branch -- do not wait for someone else to do the merge for you. Features that change ABI compatibility (such as adding MPI-3 features) should not go into 1.3.x.
I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional.
Bill: r7447 looks like a bug-fix. Can you merge it into the 1.3.x branch?
Dave: r7462 adds the qsort capability to Comm_split. Can you merge it into the 1.3.x branch?
Thanks,
-- Pavan
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
Hi Bill, The wiki page you are editing is only for actual release tarball creation. I've created a new wiki to describe the commits process: http://wiki.mcs.anl.gov/mpich2/index.php/Managing_Commits_in_Trunk_and_Relea... I've added all the details I could think of, including the ones that were discussed on this email chain. -- Pavan On 11/30/2010 07:49 PM, Pavan Balaji wrote:
One more clarification -- all commits that do not change the ABI string for 1.3.x should go into the 1.3.x branch as well. So far, this includes all commits, except the non-blocking collectives related commits. So if you haven't merged something into 1.3.x yet, please do so.
Thanks,
-- Pavan
On 11/30/2010 07:35 PM, Rajeev Thakur wrote:
There is a branch called 1.3.x.
Rajeev
On Nov 30, 2010, at 7:30 PM, William Gropp wrote:
Thanks! I'll update the release wiki page to point to these.
One question - I tried to follow the directions that Rajeev sent, and I was able to checkout a 1.3.1 release branch but not a 1.3.2 branch. I take it this means that the value of x is 1?
Bill
On Nov 30, 2010, at 2:15 PM, Dave Goodell wrote:
Like this?
https://trac.mcs.anl.gov/projects/mpich2/roadmap https://trac.mcs.anl.gov/projects/mpich2/milestone/mpich2-1.3.2
-Dave
On Nov 30, 2010, at 1:38 PM CST, William Gropp wrote:
Would it make sense to have a wiki page on the status of a release, including any outstanding bugs and whether it is still open for updates? I know we have email for this, but in looking over my email, I'm uncertain as to the status or even the value of x.
Bill
On Nov 30, 2010, at 11:32 AM, William Gropp wrote:
Thanks - I do filter mpich2-core, so cc'ing me doesn't help (that would be a useful mailer feature - overriding the filter for a list when explicitly included).
I've add this to the release page since I have it handy.
Bill
On Nov 30, 2010, at 10:25 AM, Rajeev Thakur wrote:
Bill, I have already merged r7447 from trunk to 1.3.x, but it can be done as follows:
% check out 1.3.x branch % cd into it % svn merge -c 7447 url-of-trunk . % commit
That's it.
Also, in case you are filtering mpich2-core into a read-occasionally folder, such mails (about 1.3.x) get sent there. Pavan also CCed you explicitly on some mails, but the mailer may not send it separately if you are already included in the list (at least some times it happens that way).
Rajeev
On Nov 30, 2010, at 10:01 AM, William Gropp wrote:
Pavan,
This is the first that I've heard of the 1.3.x branch - I don't even know how to do this for svn (I did know how to do it for cvs).
Is this on the wiki? I looked at http://wiki.mcs.anl.gov/mpich2/index.php/Creating_a_Release , but that suggests that a release is created from the trunk and not updated after that (except for critical fixes in the release), which is why I've tried to get things into the trunk as soon as possible.
Anyway, if you can tell me what svn commands to use and what fixes you'd like me to add, I'll be happy to do it.
(I'll put in a plea to remember that it is also everyone's responsibility to keep the documentation, both on the release process and the design documents, up to date - that discipline will save a tremendous amount of time for everyone else.)
Bill
On Nov 19, 2010, at 3:21 PM, Pavan Balaji wrote:
All,
There will very likely be a 1.3.2 release (and possibly more in the 1.3.x series) given that 1.4 has many planned features and is almost an year away.
So, whenever you commit any bug fixes to trunk, remember that it is your responsibility to merge them into the 1.3.x branch -- do not wait for someone else to do the merge for you. Features that change ABI compatibility (such as adding MPI-3 features) should not go into 1.3.x.
I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional.
Bill: r7447 looks like a bug-fix. Can you merge it into the 1.3.x branch?
Dave: r7462 adds the qsort capability to Comm_split. Can you merge it into the 1.3.x branch?
Thanks,
-- Pavan
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
Bill, I've merged your commits (r7519, r7520, r7521, r7522, r7523, r7524) to the 1.3.x branch. For future commits, can you merge them into 1.3.x? Thanks, -- Pavan On 11/30/2010 08:16 PM, Pavan Balaji wrote:
Hi Bill,
The wiki page you are editing is only for actual release tarball creation. I've created a new wiki to describe the commits process: http://wiki.mcs.anl.gov/mpich2/index.php/Managing_Commits_in_Trunk_and_Relea...
I've added all the details I could think of, including the ones that were discussed on this email chain.
-- Pavan
On 11/30/2010 07:49 PM, Pavan Balaji wrote:
One more clarification -- all commits that do not change the ABI string for 1.3.x should go into the 1.3.x branch as well. So far, this includes all commits, except the non-blocking collectives related commits. So if you haven't merged something into 1.3.x yet, please do so.
Thanks,
-- Pavan
On 11/30/2010 07:35 PM, Rajeev Thakur wrote:
There is a branch called 1.3.x.
Rajeev
On Nov 30, 2010, at 7:30 PM, William Gropp wrote:
Thanks! I'll update the release wiki page to point to these.
One question - I tried to follow the directions that Rajeev sent, and I was able to checkout a 1.3.1 release branch but not a 1.3.2 branch. I take it this means that the value of x is 1?
Bill
On Nov 30, 2010, at 2:15 PM, Dave Goodell wrote:
Like this?
https://trac.mcs.anl.gov/projects/mpich2/roadmap https://trac.mcs.anl.gov/projects/mpich2/milestone/mpich2-1.3.2
-Dave
On Nov 30, 2010, at 1:38 PM CST, William Gropp wrote:
Would it make sense to have a wiki page on the status of a release, including any outstanding bugs and whether it is still open for updates? I know we have email for this, but in looking over my email, I'm uncertain as to the status or even the value of x.
Bill
On Nov 30, 2010, at 11:32 AM, William Gropp wrote:
Thanks - I do filter mpich2-core, so cc'ing me doesn't help (that would be a useful mailer feature - overriding the filter for a list when explicitly included).
I've add this to the release page since I have it handy.
Bill
On Nov 30, 2010, at 10:25 AM, Rajeev Thakur wrote:
Bill, I have already merged r7447 from trunk to 1.3.x, but it can be done as follows:
% check out 1.3.x branch % cd into it % svn merge -c 7447 url-of-trunk . % commit
That's it.
Also, in case you are filtering mpich2-core into a read-occasionally folder, such mails (about 1.3.x) get sent there. Pavan also CCed you explicitly on some mails, but the mailer may not send it separately if you are already included in the list (at least some times it happens that way).
Rajeev
On Nov 30, 2010, at 10:01 AM, William Gropp wrote:
Pavan,
This is the first that I've heard of the 1.3.x branch - I don't even know how to do this for svn (I did know how to do it for cvs).
Is this on the wiki? I looked at http://wiki.mcs.anl.gov/mpich2/index.php/Creating_a_Release , but that suggests that a release is created from the trunk and not updated after that (except for critical fixes in the release), which is why I've tried to get things into the trunk as soon as possible.
Anyway, if you can tell me what svn commands to use and what fixes you'd like me to add, I'll be happy to do it.
(I'll put in a plea to remember that it is also everyone's responsibility to keep the documentation, both on the release process and the design documents, up to date - that discipline will save a tremendous amount of time for everyone else.)
Bill
On Nov 19, 2010, at 3:21 PM, Pavan Balaji wrote:
All,
There will very likely be a 1.3.2 release (and possibly more in the 1.3.x series) given that 1.4 has many planned features and is almost an year away.
So, whenever you commit any bug fixes to trunk, remember that it is your responsibility to merge them into the 1.3.x branch -- do not wait for someone else to do the merge for you. Features that change ABI compatibility (such as adding MPI-3 features) should not go into 1.3.x.
I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional.
Bill: r7447 looks like a bug-fix. Can you merge it into the 1.3.x branch?
Dave: r7462 adds the qsort capability to Comm_split. Can you merge it into the 1.3.x branch?
Thanks,
-- Pavan
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
I'll be happy to. Bill On Dec 1, 2010, at 1:40 AM, Pavan Balaji wrote:
Bill,
I've merged your commits (r7519, r7520, r7521, r7522, r7523, r7524) to the 1.3.x branch. For future commits, can you merge them into 1.3.x?
Thanks,
-- Pavan
On 11/30/2010 08:16 PM, Pavan Balaji wrote:
Hi Bill,
The wiki page you are editing is only for actual release tarball creation. I've created a new wiki to describe the commits process: http://wiki.mcs.anl.gov/mpich2/index.php/Managing_Commits_in_Trunk_and_Relea...
I've added all the details I could think of, including the ones that were discussed on this email chain.
-- Pavan
On 11/30/2010 07:49 PM, Pavan Balaji wrote:
One more clarification -- all commits that do not change the ABI string for 1.3.x should go into the 1.3.x branch as well. So far, this includes all commits, except the non-blocking collectives related commits. So if you haven't merged something into 1.3.x yet, please do so.
Thanks,
-- Pavan
On 11/30/2010 07:35 PM, Rajeev Thakur wrote:
There is a branch called 1.3.x.
Rajeev
On Nov 30, 2010, at 7:30 PM, William Gropp wrote:
Thanks! I'll update the release wiki page to point to these.
One question - I tried to follow the directions that Rajeev sent, and I was able to checkout a 1.3.1 release branch but not a 1.3.2 branch. I take it this means that the value of x is 1?
Bill
On Nov 30, 2010, at 2:15 PM, Dave Goodell wrote:
Like this?
https://trac.mcs.anl.gov/projects/mpich2/roadmap https://trac.mcs.anl.gov/projects/mpich2/milestone/mpich2-1.3.2
-Dave
On Nov 30, 2010, at 1:38 PM CST, William Gropp wrote:
Would it make sense to have a wiki page on the status of a release, including any outstanding bugs and whether it is still open for updates? I know we have email for this, but in looking over my email, I'm uncertain as to the status or even the value of x.
Bill
On Nov 30, 2010, at 11:32 AM, William Gropp wrote:
Thanks - I do filter mpich2-core, so cc'ing me doesn't help (that would be a useful mailer feature - overriding the filter for a list when explicitly included).
I've add this to the release page since I have it handy.
Bill
On Nov 30, 2010, at 10:25 AM, Rajeev Thakur wrote:
Bill, I have already merged r7447 from trunk to 1.3.x, but it can be done as follows:
% check out 1.3.x branch % cd into it % svn merge -c 7447 url-of-trunk . % commit
That's it.
Also, in case you are filtering mpich2-core into a read- occasionally folder, such mails (about 1.3.x) get sent there. Pavan also CCed you explicitly on some mails, but the mailer may not send it separately if you are already included in the list (at least some times it happens that way).
Rajeev
On Nov 30, 2010, at 10:01 AM, William Gropp wrote:
Pavan,
This is the first that I've heard of the 1.3.x branch - I don't even know how to do this for svn (I did know how to do it for cvs).
Is this on the wiki? I looked at http://wiki.mcs.anl.gov/mpich2/index.php/Creating_a_Release , but that suggests that a release is created from the trunk and not updated after that (except for critical fixes in the release), which is why I've tried to get things into the trunk as soon as possible.
Anyway, if you can tell me what svn commands to use and what fixes you'd like me to add, I'll be happy to do it.
(I'll put in a plea to remember that it is also everyone's responsibility to keep the documentation, both on the release process and the design documents, up to date - that discipline will save a tremendous amount of time for everyone else.)
Bill
On Nov 19, 2010, at 3:21 PM, Pavan Balaji wrote:
All,
There will very likely be a 1.3.2 release (and possibly more in the 1.3.x series) given that 1.4 has many planned features and is almost an year away.
So, whenever you commit any bug fixes to trunk, remember that it is your responsibility to merge them into the 1.3.x branch -- do not wait for someone else to do the merge for you. Features that change ABI compatibility (such as adding MPI-3 features) should not go into 1.3.x.
I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional.
Bill: r7447 looks like a bug-fix. Can you merge it into the 1.3.x branch?
Dave: r7462 adds the qsort capability to Comm_split. Can you merge it into the 1.3.x branch?
Thanks,
-- Pavan
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
Thanks, this is very helpful. Bill On Nov 30, 2010, at 8:16 PM, Pavan Balaji wrote:
Hi Bill,
The wiki page you are editing is only for actual release tarball creation. I've created a new wiki to describe the commits process: http://wiki.mcs.anl.gov/mpich2/index.php/Managing_Commits_in_Trunk_and_Relea...
I've added all the details I could think of, including the ones that were discussed on this email chain.
-- Pavan
On 11/30/2010 07:49 PM, Pavan Balaji wrote:
One more clarification -- all commits that do not change the ABI string for 1.3.x should go into the 1.3.x branch as well. So far, this includes all commits, except the non-blocking collectives related commits. So if you haven't merged something into 1.3.x yet, please do so.
Thanks,
-- Pavan
On 11/30/2010 07:35 PM, Rajeev Thakur wrote:
There is a branch called 1.3.x.
Rajeev
On Nov 30, 2010, at 7:30 PM, William Gropp wrote:
Thanks! I'll update the release wiki page to point to these.
One question - I tried to follow the directions that Rajeev sent, and I was able to checkout a 1.3.1 release branch but not a 1.3.2 branch. I take it this means that the value of x is 1?
Bill
On Nov 30, 2010, at 2:15 PM, Dave Goodell wrote:
Like this?
https://trac.mcs.anl.gov/projects/mpich2/roadmap https://trac.mcs.anl.gov/projects/mpich2/milestone/mpich2-1.3.2
-Dave
On Nov 30, 2010, at 1:38 PM CST, William Gropp wrote:
Would it make sense to have a wiki page on the status of a release, including any outstanding bugs and whether it is still open for updates? I know we have email for this, but in looking over my email, I'm uncertain as to the status or even the value of x.
Bill
On Nov 30, 2010, at 11:32 AM, William Gropp wrote:
Thanks - I do filter mpich2-core, so cc'ing me doesn't help (that would be a useful mailer feature - overriding the filter for a list when explicitly included).
I've add this to the release page since I have it handy.
Bill
On Nov 30, 2010, at 10:25 AM, Rajeev Thakur wrote:
Bill, I have already merged r7447 from trunk to 1.3.x, but it can be done as follows:
% check out 1.3.x branch % cd into it % svn merge -c 7447 url-of-trunk . % commit
That's it.
Also, in case you are filtering mpich2-core into a read- occasionally folder, such mails (about 1.3.x) get sent there. Pavan also CCed you explicitly on some mails, but the mailer may not send it separately if you are already included in the list (at least some times it happens that way).
Rajeev
On Nov 30, 2010, at 10:01 AM, William Gropp wrote:
Pavan,
This is the first that I've heard of the 1.3.x branch - I don't even know how to do this for svn (I did know how to do it for cvs).
Is this on the wiki? I looked at http://wiki.mcs.anl.gov/mpich2/index.php/Creating_a_Release , but that suggests that a release is created from the trunk and not updated after that (except for critical fixes in the release), which is why I've tried to get things into the trunk as soon as possible.
Anyway, if you can tell me what svn commands to use and what fixes you'd like me to add, I'll be happy to do it.
(I'll put in a plea to remember that it is also everyone's responsibility to keep the documentation, both on the release process and the design documents, up to date - that discipline will save a tremendous amount of time for everyone else.)
Bill
On Nov 19, 2010, at 3:21 PM, Pavan Balaji wrote:
All,
There will very likely be a 1.3.2 release (and possibly more in the 1.3.x series) given that 1.4 has many planned features and is almost an year away.
So, whenever you commit any bug fixes to trunk, remember that it is your responsibility to merge them into the 1.3.x branch -- do not wait for someone else to do the merge for you. Features that change ABI compatibility (such as adding MPI-3 features) should not go into 1.3.x.
I see that some of the windows commits (r7442, r7443, r7444, r7445) have not been merged, which I'm assuming is intentional.
Bill: r7447 looks like a bug-fix. Can you merge it into the 1.3.x branch?
Dave: r7462 adds the qsort capability to Comm_split. Can you merge it into the 1.3.x branch?
Thanks,
-- Pavan
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
participants (5)
-
Dave Goodell -
Jayesh Krishna -
Pavan Balaji -
Rajeev Thakur -
William Gropp