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.

Sign up for GitHub

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

Jump to bottom

Release process Julep #53

Open
simonbyrne opened this issue Aug 13, 2018 · 2 comments
Open

Release process Julep #53

simonbyrne opened this issue Aug 13, 2018 · 2 comments

Comments

@simonbyrne
Copy link
Contributor

simonbyrne commented Aug 13, 2018 •
edited

  • How often should we make future releases?
  • What should be the timelines and requirements for alpha, beta, RC, etc.?
  • When should we upgrade LLVM?

We should also fully document all the steps in making a release (e.g. https://github.com/JuliaLang/julia/blob/883c8a38920985e0c02df169ff8c379731d88fc6/Makefile#L112-L129)
@simonbyrne
Copy link
Contributor Author

e.g. https://forge.rust-lang.org/release-process.html

@StefanKarpinski
Copy link
Sponsor Member

My proposal is roughly:

  • Quarterly time-based releases with a month freeze before the release: anything that's merged by the month before is in, anything else isn't.
  • Not sure we need alphas and betas for minor releases, a month of release candidates might be enough.
  • Upgrade LLVM whenever LLVM is released.
  • Consider the last release of the year a "long term support release" which will get ongoing bug fix updates
  • All the other releases will get bug fix releases until the following minor release and not usually many beyond that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@StefanKarpinski @simonbyrne