You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The tentative deadline for commits is 4/8. We plan to release sometime the week of 4/12. The dates are flexible but we can also release more dot releases (e.g. 0.1.2)
If there is an issue you'd like to fix before the release, please tag it with the 0.1.1 milestone so we can track it.
In general, if the commit you wish to include looks too risky (e.g., refactors DynamicLayer :P), we might reject it or request more testing.
Logistics
If there is a commit you want to get into the release, please:
land the commit into the main branch
Create (but do not merge) a PR against the release branch (release/0.1)
Make a request below with the link to your PR against the release branch
Make sure that tests pass.
@zou3519 (or whoever's name is here) will merge the PRs into the release branch when tests pass. Please don't merge the PR yourself or it might get too hectic.
The text was updated successfully, but these errors were encountered:
The tentative deadline for commits is 4/8. We plan to release sometime the week of 4/12. The dates are flexible but we can also release more dot releases (e.g. 0.1.2)
If there is an issue you'd like to fix before the release, please tag it with the 0.1.1 milestone so we can track it.
In general, if the commit you wish to include looks too risky (e.g., refactors DynamicLayer :P), we might reject it or request more testing.
Logistics
If there is a commit you want to get into the release, please:
release/0.1
)@zou3519 (or whoever's name is here) will merge the PRs into the release branch when tests pass. Please don't merge the PR yourself or it might get too hectic.
The text was updated successfully, but these errors were encountered: