-
-
Notifications
You must be signed in to change notification settings - Fork 523
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
Migrate old Sage release tours and changelogs from Sage website and wiki to GitHub Releases or Sage documentation #31533
Comments
Migrated the list https://wiki.sagemath.org/ReleaseTours to GitHub Releases. |
Suggested to upload old release tarballs to GitHub Releases - https://groups.google.com/g/sage-devel/c/GYKHtknK-CA/m/od9nVkoHAQAJ |
Next:
|
@kwankyu re your post https://groups.google.com/g/sage-devel/c/GYKHtknK-CA/m/2Y2R2ElCAQAJ, I have done most of the above already for all releases < 4.0 |
OK. Nice! |
not yet migrated: Image attachments. |
You migrated release notes to github Releases. Does that also support image attachments? |
This comment was marked as outdated.
This comment was marked as outdated.
I deleted the fully migrated pages from https://wiki.sagemath.org/TitleIndex#idx-R and emptied those that have image attachments |
The oldest is 2.10.4. Is that the oldest version that has release notes? |
Do you mean "do not have image attachements"? For example, https://wiki.sagemath.org/ReleaseTours/sage-4.1.1?action=show&redirect=sage-4.1.1 is still there. |
I haven't touched anything for >= 4.0 yet. |
Ah right. |
Oldest is actually 2.10.1, but 2.10.4 is displayed below it for an unknown reason. Yes, I have created releases for all tags that either had individual release notes or changelog files. I had this full list already in https://wiki.sagemath.org/ReleaseTours (now gutted) |
What is your plan with releases < 2.10.1? |
No immediate plan to do anything. My priority was to migrate stuff away from the Sage wiki |
The sage release tarballs from the "old files" site are available. Do you plan to upload them to github Releases? |
I can't seem to access http://old.files.sagemath.org/src-old/; any help with the uploading is welcome |
It is working now. I thought somebody booted it up responding to you... |
No, doesn't work for me. Strange |
Anyway I may upload them, one by one slowly starting from the oldest stable version. I don't know any use of them, but perhaps just for completeness... |
Neither do I; it just serves archival purposes |
I've completed the migration for the release tours for Sage <= 9.0 now, as well as 9.2 and 9.4. |
Yes, I just added one to test it. See https://github.com/sagemath/sage/releases/tag/2.11 Update: Migrated all images now. Update: 9.1, 9.3, 9.5 have been migrated with the help of https://github.com/phlash/moin2markdown The migration of release notes from the Sage wiki is now complete. |
I have troubles in releasing sage 0.1. A. I want to attach only the old tarball. But after release, there are added one Source zip and one Source tar file automatically. |
Perhaps (A) is related with the commit to which the tag 0.1 is attached. As there is no commit that can be associated with the tag 0.1, it seems inappropriate to push these pre-git releases to github "Releases".... |
I agree. Let's skip old releases that do not correspond to an existing tag in the repository. |
… tours links <!-- ^ Please provide a concise and informative title. --> <!-- ^ Don't put issue numbers in the title, do this in the PR description below. --> <!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method to calculate 1 + 2". --> <!-- v Describe your changes below in detail. --> <!-- v Why is this change required? What problem does it solve? --> <!-- v If this PR resolves an open issue, please link to it here. For example, "Fixes sagemath#12345". --> The release tours are now accessed through GitHub Releases. This is the next step of: - sagemath#31533 ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> - [x] The title is concise and informative. - [x] The description explains in detail what this PR is about. - [x] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation and checked the documentation preview. ### ⌛ Dependencies <!-- List all open PRs that this PR logically depends on. For example, --> <!-- - sagemath#12345: short description why this is a dependency --> <!-- - sagemath#34567: ... --> URL: sagemath#38581 Reported by: Matthias Köppe Reviewer(s): Kwankyu Lee
… tours links <!-- ^ Please provide a concise and informative title. --> <!-- ^ Don't put issue numbers in the title, do this in the PR description below. --> <!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method to calculate 1 + 2". --> <!-- v Describe your changes below in detail. --> <!-- v Why is this change required? What problem does it solve? --> <!-- v If this PR resolves an open issue, please link to it here. For example, "Fixes sagemath#12345". --> The release tours are now accessed through GitHub Releases. This is the next step of: - sagemath#31533 ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> - [x] The title is concise and informative. - [x] The description explains in detail what this PR is about. - [x] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation and checked the documentation preview. ### ⌛ Dependencies <!-- List all open PRs that this PR logically depends on. For example, --> <!-- - sagemath#12345: short description why this is a dependency --> <!-- - sagemath#34567: ... --> URL: sagemath#38581 Reported by: Matthias Köppe Reviewer(s): Kwankyu Lee
… tours links <!-- ^ Please provide a concise and informative title. --> <!-- ^ Don't put issue numbers in the title, do this in the PR description below. --> <!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method to calculate 1 + 2". --> <!-- v Describe your changes below in detail. --> <!-- v Why is this change required? What problem does it solve? --> <!-- v If this PR resolves an open issue, please link to it here. For example, "Fixes sagemath#12345". --> The release tours are now accessed through GitHub Releases. This is the next step of: - sagemath#31533 ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> - [x] The title is concise and informative. - [x] The description explains in detail what this PR is about. - [x] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation and checked the documentation preview. ### ⌛ Dependencies <!-- List all open PRs that this PR logically depends on. For example, --> <!-- - sagemath#12345: short description why this is a dependency --> <!-- - sagemath#34567: ... --> URL: sagemath#38581 Reported by: Matthias Köppe Reviewer(s): Kwankyu Lee
… tours links <!-- ^ Please provide a concise and informative title. --> <!-- ^ Don't put issue numbers in the title, do this in the PR description below. --> <!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method to calculate 1 + 2". --> <!-- v Describe your changes below in detail. --> <!-- v Why is this change required? What problem does it solve? --> <!-- v If this PR resolves an open issue, please link to it here. For example, "Fixes sagemath#12345". --> The release tours are now accessed through GitHub Releases. This is the next step of: - sagemath#31533 ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> - [x] The title is concise and informative. - [x] The description explains in detail what this PR is about. - [x] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation and checked the documentation preview. ### ⌛ Dependencies <!-- List all open PRs that this PR logically depends on. For example, --> <!-- - sagemath#12345: short description why this is a dependency --> <!-- - sagemath#34567: ... --> URL: sagemath#38581 Reported by: Matthias Köppe Reviewer(s): Kwankyu Lee
… tours links <!-- ^ Please provide a concise and informative title. --> <!-- ^ Don't put issue numbers in the title, do this in the PR description below. --> <!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method to calculate 1 + 2". --> <!-- v Describe your changes below in detail. --> <!-- v Why is this change required? What problem does it solve? --> <!-- v If this PR resolves an open issue, please link to it here. For example, "Fixes sagemath#12345". --> The release tours are now accessed through GitHub Releases. This is the next step of: - sagemath#31533 ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> - [x] The title is concise and informative. - [x] The description explains in detail what this PR is about. - [x] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation and checked the documentation preview. ### ⌛ Dependencies <!-- List all open PRs that this PR logically depends on. For example, --> <!-- - sagemath#12345: short description why this is a dependency --> <!-- - sagemath#34567: ... --> URL: sagemath#38581 Reported by: Matthias Köppe Reviewer(s): Kwankyu Lee
… tours links <!-- ^ Please provide a concise and informative title. --> <!-- ^ Don't put issue numbers in the title, do this in the PR description below. --> <!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method to calculate 1 + 2". --> <!-- v Describe your changes below in detail. --> <!-- v Why is this change required? What problem does it solve? --> <!-- v If this PR resolves an open issue, please link to it here. For example, "Fixes sagemath#12345". --> The release tours are now accessed through GitHub Releases. This is the next step of: - sagemath#31533 ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> - [x] The title is concise and informative. - [x] The description explains in detail what this PR is about. - [x] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation and checked the documentation preview. ### ⌛ Dependencies <!-- List all open PRs that this PR logically depends on. For example, --> <!-- - sagemath#12345: short description why this is a dependency --> <!-- - sagemath#34567: ... --> URL: sagemath#38581 Reported by: Matthias Köppe Reviewer(s): Kwankyu Lee
… tours links <!-- ^ Please provide a concise and informative title. --> <!-- ^ Don't put issue numbers in the title, do this in the PR description below. --> <!-- ^ For example, instead of "Fixes sagemath#12345" use "Introduce new method to calculate 1 + 2". --> <!-- v Describe your changes below in detail. --> <!-- v Why is this change required? What problem does it solve? --> <!-- v If this PR resolves an open issue, please link to it here. For example, "Fixes sagemath#12345". --> The release tours are now accessed through GitHub Releases. This is the next step of: - sagemath#31533 ### 📝 Checklist <!-- Put an `x` in all the boxes that apply. --> - [x] The title is concise and informative. - [x] The description explains in detail what this PR is about. - [x] I have linked a relevant issue or discussion. - [ ] I have created tests covering the changes. - [ ] I have updated the documentation and checked the documentation preview. ### ⌛ Dependencies <!-- List all open PRs that this PR logically depends on. For example, --> <!-- - sagemath#12345: short description why this is a dependency --> <!-- - sagemath#34567: ... --> URL: sagemath#38581 Reported by: Matthias Köppe Reviewer(s): Kwankyu Lee
Following the practices of many other projects, we make old release notes (release tours; but not changelogs)
part of the normal documentationavailable on the GitHub Releases.This is one more step to getting rid of the wiki.
Related: #31415 GH Actions workflow that deploys built documentation
CC: @slel
Component: documentation
Issue created by migration from https://trac.sagemath.org/ticket/31533
The text was updated successfully, but these errors were encountered: