Nope - 1.5 is completed and will now be rotated to 1.6 in the near future. The trunk will be branched to create the new 1.7 series, and then released this summer. Your module can go in there, I suspect.
On Apr 14, 2012, at 4:45 PM, Alex Margolin wrote:
> On 04/15/2012 12:36 AM, Ralph Castain wrote:
>> The 1.6 branch is a stable series - no new features will be added to it, so your patch won't be going there. I'd focus solely on the trunk.
> - Can I add my module(s) to 1.5 branch? (as well as the trunk?)
>> What you're doing with he RAS is fine for now. In the next few days, I'll be changing the API to the RAS components, but it isn't a big change and we can adjust as you get closer. The orte_job_t object does contain the number of procs to be launched prior to the RAS being invoked, but you have to compute it. Each app_context contains that number - so to get it for the job, you cycle across all the app_contexts and add it up.
>> The mapper assigns the final num_procs value in the orte_job_t object. We do this because the user can also run the job without specifying the number of procs, and we'll simply run one proc for every allocated slot. It's a popular option, but wouldn't work here for obvious reasons.
> devel mailing list