Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release #201

Closed
nrdxp opened this issue Dec 14, 2022 · 7 comments
Closed

Release #201

nrdxp opened this issue Dec 14, 2022 · 7 comments

Comments

@nrdxp
Copy link
Contributor

nrdxp commented Dec 14, 2022

We need to cut a release. We have divnix/std-action now and we need to provide some level of interoperability between the two. We can't do that to any level of sanity without tracking a stable target. It doesn't have to be 1.0 but we need to cut something. x-ref: divnix/std-action#17

@blaggacao
Copy link
Collaborator

I'm clandestinely waiting for https://github.com/jmgilman/cocogitto-pr, which is clandestinely waiting for std-action in turn 😃 .

But as soon as that's in place, we should be able to do this rather swiftly.

@blaggacao
Copy link
Collaborator

blaggacao commented Dec 18, 2022

Deliberate dependency on #121

@nrdxp
Copy link
Contributor Author

nrdxp commented Dec 19, 2022

Its not a hard dependency though right? The cocogitto PR action just adds a nice preview of the changelog. Not sure why that would block a release.

@blaggacao
Copy link
Collaborator

blaggacao commented Dec 19, 2022

Its not a hard dependency though right?

No, deliberate. To properly exercise the process and ritual. It also puts stretchy time bounds on the cocogitto-pr milestone.

@jmgilman
Copy link
Collaborator

I agree it shouldn't be a hard dependency. It's possible to integrate cocogitto without the existence of the PR generation, which is really just a nicety in the end.

@blaggacao
Copy link
Collaborator

Another aspect, I didn't mention, but had in mind is to land a release of std together with 1.0 releases of the satellite repos (nosys / data-merge / yants / incl / paisano).

If we package this properly, it can be a true milestone for the project (not just a release).

@blaggacao
Copy link
Collaborator

blaggacao commented Dec 20, 2022

Let me actually transform this into a milestone via Github Settings. Closing here.

I'll do that tomorrow.

@blaggacao blaggacao closed this as not planned Won't fix, can't repro, duplicate, stale Dec 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants