-
Notifications
You must be signed in to change notification settings - Fork 695
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
Publishing prereleases – Suggest -wip
for naming convention during development
#2453
Comments
I'm confused, because we have an internal team practice on a few packages, we now want to change our external guidance for how our customers should do it? I like the current guidance; using Wouldn't it be simpler to change our internal practice to use something like |
I don't think we need to be overly prescriptive here, I would definitely not add a warning or error to pub. Given that we are going to start publishing pre-release versions then I agree with @mit-mit that we should reconsider how we are managing the "in progress" versions as the current |
I'm fine going either way – just pushing for consistency here. A lot of folks follow along w/ our repos and assume we're always using best practices. |
Didn't mean to close! |
@mit-mit , @kevmoo , @jakemac53 : Is this still a going concern? If so, do you have any updates? |
WDYT about |
|
CC @devoncarew – would be good to get this into our tooling if this is our new protocol. |
I like |
No opinion here, happy to use whatever suffix. |
-wip
for naming convention during development
Sounds like there has been consensus on using Unless someone chimes in, the task here is now:
Thanks all! |
Page URL: https://dart.dev/tools/pub/publishing#publishing-prereleases
Page source: https://github.com/dart-lang/site-www/tree/master/src/tools/pub/publishing.md
We tend to use
-dev
as a suffix for packages during development – only changing it before we publish. This makes it easy for someone looking at the source to understand the state of the package. See https://github.com/dart-lang/sdk/wiki/External-Package-MaintenanceFirst, should be generalize this convention?
If yes, we should update this page. Use
-alpha
or-beta
If yes, we may also want to go as far as adding a warning (or error) to the pub client.
CC @mit-mit @jakemac53 @natebosch @kwalrath
The text was updated successfully, but these errors were encountered: