Skip to content

CHGL release#16

Open
LouisJenkinsCS wants to merge 2 commits intochapel-lang:masterfrom
LouisJenkinsCS:chgl-release
Open

CHGL release#16
LouisJenkinsCS wants to merge 2 commits intochapel-lang:masterfrom
LouisJenkinsCS:chgl-release

Conversation

@LouisJenkinsCS
Copy link
Member

@LouisJenkinsCS LouisJenkinsCS commented Apr 2, 2019

Chapel HyperGraph Library (CHGL) Release for Mason Repository

Repository: https://github.com/pnnl/chgl

@LouisJenkinsCS
Copy link
Member Author

Calling @tjstavenger-pnnl to take over

@tjstavenger-pnnl
Copy link

It looks like we have some work to do yet on getting our CHGL repo setup to be a Mason package. I think we should hold off on merging this pull request, though eventually we'll be ready.

@tjstavenger-pnnl
Copy link

tjstavenger-pnnl commented Aug 19, 2019

The current mason test fails for CHGL due to chapel-lang/chapel#7106 features:

We'd like to release CHGL as a Mason package, but are there requirements for how it works (i.e., mason test passes) before acceptance?

@ben-albrecht
Copy link
Member

ben-albrecht commented Aug 22, 2019

Ideally mason test would be passing, although it's not a hard requirement currently (this will be changing as testing infrastructure improves).

Other than that, we just validate the package metadata is correct.

@tjstavenger-pnnl - do you think it's ready for review?

@LouisJenkinsCS
Copy link
Member Author

I believe it's fine to tag the current state as v0.20 @tjstavenger-pnnl and release that

@ben-albrecht
Copy link
Member

I believe it's fine to tag the current state as v0.20 @tjstavenger-pnnl and release that

Just to clarify, did you mean 0.2.0?

@tjstavenger-pnnl
Copy link

If Cray is OK with mason test failing, but start_test passing, then we should be ready for review once we release v0.2.0

@ben-albrecht
Copy link
Member

@tjstavenger-pnnl - OK, just ping me here when v0.2.0 is out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants