Good point. I think it would be worthwhile to keep the 1.2.1 data (e.g., make a new wiki page with "1.2.1" in the filename somehow. I.e., we have the data, so we might as well keep it -- especially in early days of libfabric, it may well be useful (user asks, "I'm using libfabric vX.Y, but Z doesn't work..." / "Oh, you should upgrade to vA.B; the matrix shows that Z isn't support in vX.Y").
And we should keep https://github.com/ofiwg/libfabric/wiki/Provider-Feature-Matrix to always be the current release. > On Mar 14, 2016, at 5:05 PM, Dave Goodell (dgoodell) <[email protected]> > wrote: > > Another good pre-1.3-release task for provider maintainers would be to update > the provider feature matrix: > > https://github.com/ofiwg/libfabric/wiki/Provider-Feature-Matrix > > If you get some time as we approach the release, please update the columns > for your respective providers. Optionally, we also could archive the current > state to indicate support as of the 1.2.1 release, though I'm not sure how > often users/developers will need such historical information. > > -Dave > > _______________________________________________ > ofiwg mailing list > [email protected] > http://lists.openfabrics.org/mailman/listinfo/ofiwg -- Jeff Squyres [email protected] For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/ _______________________________________________ ofiwg mailing list [email protected] http://lists.openfabrics.org/mailman/listinfo/ofiwg
