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

SPEC Tools: tool to support calendar for SPEC0 #173

Closed
bsipocz opened this issue Apr 4, 2023 · 9 comments
Closed

SPEC Tools: tool to support calendar for SPEC0 #173

bsipocz opened this issue Apr 4, 2023 · 9 comments
Assignees

Comments

@bsipocz
Copy link
Member

bsipocz commented Apr 4, 2023

Ideally, the SPEC sets the logic of the versions, but the actual release and dates are not hard-wired in it but are provided by a separate tool.

@bsipocz
Copy link
Member Author

bsipocz commented May 23, 2023

version.py in the spec0 directory does parts of this. I think it should be moved outside of this policies repo into a tools repo, as well as the spec source docs to be cleaned up from all hard-wired version information, so this issues is probably shouldn't be closed just yet.

@munkm
Copy link
Member

munkm commented May 23, 2023

What if we create a utils/ folder in this repo that holds all of our SPEC utility tools? Then other orgs/projects can use the tools associated with the specs, and their association with the SPECs are obvious?

@bsipocz
Copy link
Member Author

bsipocz commented May 24, 2023

OK, the remaining points to actually auto generate both the figure, and the drop text table using the script.

I suppose some JS wizardry would do the trick.

@bsipocz
Copy link
Member Author

bsipocz commented May 24, 2023

@alphapapa - this maybe something for you? We already have the python script that generates the dates, but didn't massaged it into a CI cron to auto generate the figure and the drop table in for the SPEC0 rendering.
Ideally, it would be wonderful not to have those in the md file altogether, but pulled in from a generated file?

@alphapapa
Copy link
Contributor

@bsipocz Hi, sure, I'd be glad to work on this, assuming that @jarrodmillman / @stefanv agree. :)

@bsipocz
Copy link
Member Author

bsipocz commented May 24, 2023

Yeap, Jarrod was standing by my shoulders when I made the comment :)

@alphapapa
Copy link
Contributor

Haha, great. :) I'll assign this to myself and put it in my list. Thanks.

@alphapapa
Copy link
Contributor

@bsipocz Oh, apparently I can't assign issues on this repo. Would you assign it to me please?

jarrodmillman pushed a commit that referenced this issue May 31, 2023
The issue mentioned in #218, but I like to keep that one open as a thing
to pay attention to when doing
#173
@bsipocz
Copy link
Member Author

bsipocz commented Sep 27, 2024

The process we converged on is good in practice, so I'm closing this issue.

@bsipocz bsipocz closed this as completed Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants