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

Start merging post release now? #1640

Closed
SteveBronder opened this issue Jan 24, 2020 · 3 comments
Closed

Start merging post release now? #1640

SteveBronder opened this issue Jan 24, 2020 · 3 comments

Comments

@SteveBronder
Copy link
Collaborator

Description

We have a pretty decent sized backlog of PRs to merge. Should we do them in some order and all the other ones have to merge after? We should get on it soon since the testing will have to sound off for each one

Current Version:

v3.1.0
@rok-cesnovar
Copy link
Member

Lets wait for cmdstan to release (should happen soon) just to be safe and then go by number, starting with #1558 and on. Poor Jenkins will be pretty busy over the weekend :)

@rok-cesnovar
Copy link
Member

rok-cesnovar commented Jan 24, 2020 •
edited
Loading

1558, 1602, 1603, 1618, 1626, 1630, 1632, 1634 are all approved or have a comment that they are gtg after release. It might be best if someone volunteers and merges them one by one.

EDIT: Cmdstan released, we can move.

@rok-cesnovar
Copy link
Member

Everything merged, lets close once this batch of merge-to-develop tests all pass.

@mcol mcol closed this as completed Jan 27, 2020
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
3 participants
@SteveBronder @mcol @rok-cesnovar