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

Need t/spectest.data.6.d #2557

Closed
zoffixznet opened this issue Dec 21, 2018 · 1 comment
Closed

Need t/spectest.data.6.d #2557

zoffixznet opened this issue Dec 21, 2018 · 1 comment
Labels
meta Repo organization, code style, etc.

Comments

@zoffixznet
Copy link
Contributor

zoffixznet commented Dec 21, 2018

In Rakudo's repo, we have several files that list which roast test files the test suite needs to run. If 6.c roast is being tested, t/spectest.data.6.c will be used. And by default, t/spectest.data will be used, which is typically used by roast master branch, which contains proposals for the next language version.

Since 6.d spec was released, we need to create t/spectest.data.6.d file, based on current t/spectest.data.

There are some docs for how this system works: https://github.com/rakudo/rakudo/blob/master/docs/roast-spectest.data-versioning.md

Also, 6.d release forgot to update the VERSION file. Filed as Raku/roast#506

@zoffixznet zoffixznet added the meta Repo organization, code style, etc. label Dec 21, 2018
@zoffixznet zoffixznet changed the title Need t/spectest.data.d Need t/spectest.data.6.d Dec 21, 2018
@vrurg
Copy link
Member

vrurg commented May 31, 2019

With regard to Raku/problem-solving#31 discussion, revision-specific files are not needed. To mark milestones and revision statuses tags and branches are used: 6.<revision> tag on master as a watershed between previous and following PREVIEWs and 6.<revision>-errata branch for changes specific to that particular release.

@vrurg vrurg closed this as completed May 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Repo organization, code style, etc.
Projects
None yet
Development

No branches or pull requests

2 participants