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

First release #2

Closed
vaygr opened this issue Sep 20, 2022 · 4 comments
Closed

First release #2

vaygr opened this issue Sep 20, 2022 · 4 comments

Comments

@vaygr
Copy link

vaygr commented Sep 20, 2022

I'm planning to create a mimi package for a couple of distributions, and it might be easier if they were based on a release. I think it makes sense to use an active fork.

Does it make sense to cut a tag and make the first release?

@BachoSeven
Copy link
Owner

Sure, might as well. I am not at all familiar with versioning this kind of scripts, should I just do 1.0.0 and call it a day?

@BachoSeven
Copy link
Owner

https://semver.org/ suggests to use v0.1.0, I'll go with that

@BachoSeven
Copy link
Owner

BachoSeven commented Sep 21, 2022

@vaygr let me know if you need any further help with packagin, I only made a quick AUR package sometime ago:

https://aur.archlinux.org/packages/mimi-bachoseven-git

Actually, I noticed you commented on mimi-git, and since it is orphan I will adopt it and merge the former into it, as it's not maintained.

I'll also make a "stable" release on the AUR under mimi.

@vaygr
Copy link
Author

vaygr commented Sep 21, 2022

I'll also make a "stable" release on the AUR under mimi

Yeah, that's what I was going to do. Thanks! Some just want to rely on strict releases rather than bleeding edge git commits.

I'll update the mimi package for the distribution I maintain.

Thanks again!

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

2 participants