-
Notifications
You must be signed in to change notification settings - Fork 65
25.12 - updated Maintainer Docs - Release Planning #715
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
base: main
Are you sure you want to change the base?
25.12 - updated Maintainer Docs - Release Planning #715
Conversation
✅ Deploy Preview for docs-rapids-ai ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
ok now that we ahve the labels sorted out... I put this up as a draft PR as therei s one key thing I don't know about. This page includes a link to a centralized release dashboard of some sort... it originally pointed to a specific repository in I added one of the seemingly related "release dashboards" that ops used during the release itself created by @AyodeAwe , but I don't think that's correct either. Will need some input to get this set up and aligned with the current release planning paradim and discuss it with @mmccarty as I believe he has been one of the folks driving the rapids planning. |
…his once we decide what we want to do here
|
This looks like very old docs, older than my time here. @bdice do you possibly have context on the page @rockhowse is updating here? @rockhowse I think you're correct to use one of the release dashboards we've used in recent past. You probably want to involve @caryr35 here as well as he's got a lot of coverage in the area of "release planning". |
|
I pinged @caryr35 and the dashboard and his initial response was that we don't really have an "all rapids release board" we can link to currently. The original one linked to If we don't have a "rapids release board" vs one per repo we remove it for now and instead update it later with a more comprehensive view (maybe board/repo etc.) |
|
Nowadays each project uses their own board and their own planning process. I would delete this page. |
This PR updates the Release Planning section
to bring it up to the current planning/release process post RSN-47
This focuses on using
CALVER (YY.MM.PP)instead and + an un-changingmaindevelopment branchxref: rapidsai/build-planning#224