Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

Release process: consider using beta versions #645

Closed
JoshuaKGoldberg opened this issue Nov 6, 2018 · 1 comment
Closed

Release process: consider using beta versions #645

JoshuaKGoldberg opened this issue Nov 6, 2018 · 1 comment
Labels
Domain: Releases Scheduling and infrastructure around package releases. Type: Question
Milestone

Comments

@JoshuaKGoldberg
Copy link

I'm planning on flighting a 6.0.0-beta0 before 6.0.0. Should this be part of the regular process?

@JoshuaKGoldberg JoshuaKGoldberg added Type: Question Domain: Tooling Repository tasks around improving source tooling. labels Nov 6, 2018
@IllusionMH
Copy link
Contributor

IllusionMH commented Nov 6, 2018

It is good idea.
6.x is good start for this practice, but I'm not familiar with audience and ways how they get new versions, and how long to wait for feedback for this first beta.

Few point may be addressed to make this flow more effective:

  • at this point there are no docs for devs on how to get preview (alpha/beta/insiders) builds (probably tag next as in TypsScript)
  • tag in npm to simplify getting new preview releases
  • recommendations where to use preview versions and what to expect
  • perhaps some info channel

P.S. nit: is it -beta0 or -beta.0. Later format (with ., more readable) is used for TS, TSLint, React, Babel and former I've find only in Office Fabric UI.

@JoshuaKGoldberg JoshuaKGoldberg added Domain: Releases Scheduling and infrastructure around package releases. and removed Domain: Tooling Repository tasks around improving source tooling. labels Jan 2, 2019
@IllusionMH IllusionMH added this to the None milestone May 18, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Domain: Releases Scheduling and infrastructure around package releases. Type: Question
Projects
None yet
Development

No branches or pull requests

2 participants