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

User Survey in an issue: Anything we should change for 1.0? #135

Open
bwplotka opened this issue Feb 21, 2023 · 2 comments
Open

User Survey in an issue: Anything we should change for 1.0? #135

bwplotka opened this issue Feb 21, 2023 · 2 comments
Labels
question Further information is requested

Comments

@bwplotka
Copy link
Owner

Hi,

It's time of the tool stability in terms of flags and behaviour, that I would love to consider releasing v1.0 finally (: This means no flag and option can change without breaking change. In terms of .bingo directory structure, any changes would need to be also limited, however with migration scheme as I was doing we could change things. In v1.0 we can also add more stuff.

Please add +1 emoji if you don't have objections. If you have some wishes towards API, now is time to comment here! 🤗

I will be waiting until EOM March, then release v1.0.

@bwplotka bwplotka added the question Further information is requested label Feb 21, 2023
@kishaningithub
Copy link

Not sure if this the right place to put this, i would like to have a bingo get -u option similar to go get -u to upgrade all my dependencies using a single command

@bwplotka
Copy link
Owner Author

No, it's a good mention. However we can totally add this after 1.0 (: Added #139 for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants