+1 too

Ralph, just to be clear ...
from a mtt point of view, do you expect only a release tag and a tarball ?
or do you also expect a .spec file
(iirc, OpenHPC is RPM based even if they use their own .spec file)



On 12/10/2015 11:34 PM, Jeff Squyres (jsquyres) wrote:
+1.  We did do a release branch at one point (which is likely completely stale), but 
we've never invested any release engineering efforts into MTT to make a packaged/perfect 
tarball -- mainly because, at least in the beginning, MTT was just for Open MPI core 
developers, and we were comfortable telling them "get a source checkout and run from 

If MTT is growing up to be a real package in OpenHPC, then it probably does 
need to get some release engineering lovin'.

On Dec 10, 2015, at 4:47 AM, Josh Hursey <jjhur...@open-mpi.org> wrote:

I think that would be good. I won't have any cycles to help until after the 
first of the year. We started working towards a release way back when, but I 
think we got stuck with the license to package up the graphing library for the 
MTT Reporter. We could just remove that feature from the release since the new 
reporter will do something different.

Releasing where we are now should be pretty straight forward if folks just want 
to posted a versioned tarball. We would have to assess how to get MTT into a 
more packaged configuration (e.g., rpm) if folks want that.

On Wed, Dec 9, 2015 at 11:36 AM, Ralph Castain <r...@open-mpi.org> wrote:
Hey folks

There is interest in packaging MTT in the OpenHPC distribution. However, we don't 
actually have "releases" of MTT. Any objection to actually tagging/releasing 


mtt-users mailing list
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
Searchable archives: 

Joshua Hursey
Assistant Professor of Computer Science
University of Wisconsin-La Crosse
mtt-users mailing list
Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/mtt-users
Link to this post: 

Reply via email to