-
Notifications
You must be signed in to change notification settings - Fork 164
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
convert Changes manuals book into markdown #3886
Conversation
tests are failing, but nothing to do with this PR |
Thanks. Others can see rendered markdown at https://github.com/dimpase/gap/blob/master/doc/Changes.md Questions so far:
Furthermore, I suspect failing tests are because of this PR:
since it tried to load the now missing manual book. Other diffs are perhaps of the same reason. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
doc/Changes.md
Outdated
and therefore is no longer distributed with | ||
**GAP**. | ||
|
||
#### 2.2 **GAP** 4.10.1 (February 2019) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So right now the order of releases in this file is:
- 4.11.0
- 4.10.0
- 4.10.1
- 4.10.2
- 4.9.0
- 4.9.1
- ...
That's not good. We should permute it.
I'm trying to fix the failing test |
what the fresh hell is
I'm trying to builf this branch using the packages-stable-4.11 tarball, in case |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @dimpase for cleaning this up - we have a good progress, hope we can merge this tomorrow and do release wrapping on the weekend. Please change the spelling of the filename to CHANGES.md
and put it in the root directory, not where it is now,
do you have any idea why I can't build the doc anymore. I tried on two different boxes... |
|
@dimpase yes: go to
I think this is due to all cross-references from manuals to |
@dimpase Hopefully only two places:
|
right, just cleaned these up, testing |
OK - it's now available for preview at https://github.com/dimpase/gap/blob/master/CHANGES.md |
These are historical texts. I would not change URLs or add "UPDATE 2020" links, unless you are willing to commit to check and update ALL links, and during every release. And frankly I'd still be against it because I wouldn't be sure you'd be able to stick to such a commitment for multiple years (no offense intended, I wouldn't trust that with myself either) |
let the historians of maths software care about broken URLs - and before this PR they were present too, so that's not a regression to keep it this way. |
For historians of math software https://archiveprogram.github.com/ says that GAP will go to Svalbard: "The 02/02/2020 snapshot archived in the GitHub Arctic Code Vault will sweep up every active public GitHub repository, in addition to significant dormant repos. The snapshot will include every repo with any commits between the announcement at GitHub Universe on November 13th and 02/02/2020, every repo with at least 1 star and any commits from the year before the snapshot (02/03/2019 - 02/02/2020), and every repo with at least 250 stars." |
@dimpase if you could address my remarks about the number of manual books and missing mentions of the HPC-GAP manual, perhaps this will be ready for merging... |
@alex-konovalov I adjusted the number of books as Changes stopped being one. And adding HPC-GAP as a "new" book probably needs another PR - is there a consensus that it's mature and useful enough on its own to be promoted to this level? |
@dimpase That book is "official" in a sense that it's linked from https://www.gap-system.org/Doc/manuals.html |
@alex-konovalov OK, done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good - left just one comment about README.md. @fingolfin are you happy to merge?
doc/README.md
Outdated
respectively. Some documentation is also stored in the library files to be kept | ||
close to the code it describes. It is included in the manual using the mechanism | ||
documented [here](https://www.gap-system.org/Manuals/pkg/GAPDoc-1.5.1/doc/chap4.html). | ||
documented [here](https://www.gap-system.org/Manuals/pkg/GAPDoc-1.6.2/doc/chap4.html). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could be done separately, but why not now?
@alex-konovalov : this has been fixed already:
cf. https://github.com/dimpase/gap/blob/master/doc/README.md |
@dimpase sorry was unclear: the suggestion was not to update GAPDoc version number in the URL, but replace by http://www.math.rwth-aachen.de/~Frank.Luebeck/GAPDoc/doc/chap4.html which does not depend on the version number. https://github.com/dimpase/gap/blob/master/doc/README.md has two hyperlinks for GAPDoc, one to GAP website, one to its Aachen homepage. |
done by dimpase@d865442 |
Thanks @dimpase - hope that was last change before merging this. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just pushed a few more very minor changes, and am happy with the result now. Lets "squash & merge"?
Also, many thanks to @dimpase for working on this! |
Squash and merge PR #3886: - convert Changes manual into a single markdown file - add GAP 4.11 release notes Co-authored by Dima Pasechnik and Max Horn
Backported to |
Looking at release wrapping scripts, I see this in
|
Convert Changes manuals book into markdown
Text for release notes
Changed are no longer a Manual's "book", butr just a markdown file
Further details
If necessary, please provide further details here.
Checklist for pull request reviewers
If your code contains kernel C code, run
clang-format
on it; thesimplest way is to use
git clang-format
, e.g. like this (don'tforget to commit the resulting changes):
usage of relevant labels
release notes: not needed
orrelease notes: to be added
bug
orenhancement
ornew feature
stable-4.X
add thebackport-to-4.X
labelbuild system
,documentation
,kernel
,library
,tests
runnable tests
lines changed in commits are sufficiently covered by the tests
adequate pull request title
well formulated text for release notes
relevant documentation updates
sensible comments in the code