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

Update the version to 0.0.20 #5082

Merged
merged 1 commit into from
Jul 14, 2023
Merged

Update the version to 0.0.20 #5082

merged 1 commit into from
Jul 14, 2023

Conversation

sylvestre
Copy link
Contributor

No description provided.

@tertsdiepraam
Copy link
Member

What is your long-term plan for versioning? In other words, when do we move to 0.1, or 1.0? I suppose we go to 1.0 once we pass a large majority of the GNU tests? Do you want to go to 0.x before that?

For this release just bumping to 0.0.20 is fine of course. I'm just wondering because I don't think we ever discussed this.

@github-actions
Copy link

GNU testsuite comparison:

Skipping an intermittent issue tests/tail-2/inotify-dir-recreate

@sylvestre sylvestre merged commit 8093d81 into uutils:main Jul 14, 2023
44 of 45 checks passed
@sylvestre sylvestre deleted the version branch July 14, 2023 12:08
@sylvestre
Copy link
Contributor Author

For this release just bumping to 0.0.20 is fine of course. I'm just wondering because I don't think we ever discussed this.

I was just thinking 1 when we are almost at GNU testsuite results :)
and do 0.0.X+1 but I don't have strong opinions on this

@tertsdiepraam
Copy link
Member

Sounds good! I figured that was the idea, but it's good to have it confirmed. I think it's a good strategy.

@sylvestre
Copy link
Contributor Author

@tertsdiepraam actually, i have a new proposition :)

We still keep the aim at 1.0.0 more or less equivalent to GNU

But until then, 0.Y.0 and Y being the number of GNU tools with full GNU successful coverage
WDYT? (there is the question of regression but we can probably leave with this)

@tertsdiepraam
Copy link
Member

That's nice too! I was thinking something similar where 0.2.0 would mean passing around 20% GNU tests or something. And then we increment Z with every release where we don't cross that threshold.

@tertsdiepraam
Copy link
Member

I've made an issue for this to make this discussion a bit more visible for contributors: #5083

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

Successfully merging this pull request may close these issues.

2 participants