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.

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

Packages: monitoring readiness for GAP 4.10 #2804

Closed
29 of 50 tasks
olexandr-konovalov opened this issue Sep 12, 2018 · 16 comments
Closed
29 of 50 tasks

Packages: monitoring readiness for GAP 4.10 #2804

olexandr-konovalov opened this issue Sep 12, 2018 · 16 comments
Labels
topic: packages issues or PRs related to package handling, or specific to a package (for packages w/o issue tracker)
Milestone

Comments

@olexandr-konovalov
Copy link
Member

olexandr-konovalov commented Sep 12, 2018

This is an issue to monitor the status of selected packages for which an update is desired in time for GAP 4.10. We are not currently aware about any packages for which the absence of the new release will block us from publishing GAP 4.10, but for some packages making their new release should be a task of a high priority.

CRITICAL

HIGHLY DESIRABLE

GOOD TO HAVE

PULL REQUESTS BLOCKED BY PACKAGES

WINDOWS ISSUES
Need also to check that as many as possible packages with binaries are usable under Windows.

Please feel free to edit this issue and add more packages to the checklist.

@olexandr-konovalov olexandr-konovalov added the topic: packages issues or PRs related to package handling, or specific to a package (for packages w/o issue tracker) label Sep 12, 2018
@olexandr-konovalov olexandr-konovalov added this to the GAP 4.10.0 milestone Sep 12, 2018
@olexandr-konovalov olexandr-konovalov changed the title Tracking package readiness for GAP 4.10 Packages: monitoring readiness for GAP 4.10 Sep 12, 2018
@fingolfin
Copy link
Member

Note that I believe the LOOP and FR issue is caused by issue #2513, which is fixed by @stevelinton's PR #2773. However, I don't think that PR is good for 4.10, it's too risky for that. But at least for 4.11 that's fine.

@olexandr-konovalov
Copy link
Member Author

Ticked boxes for CAP project, groupoids, guarana, KBMAG, MapClass, ModIsom, Wedderga.

@markuspf
Copy link
Member

JupyterKernel is of course still broken

@olexandr-konovalov
Copy link
Member Author

@markuspf I've added JupyterKernel to the list - could you please add links to the issues in its issue tracker which have to be resolved?

@fingolfin
Copy link
Member

I made a new release of guarana, it should fix the issue with it.

@markuspf
Copy link
Member

markuspf commented Sep 22, 2018

JupyterKernel is fixed, but there's a rather delicate issue (gap-packages/smallgrp#38) with the smallgrp package.

@olexandr-konovalov
Copy link
Member Author

Ticked boxes for automata, guarana, JupyterKernel.

@olexandr-konovalov
Copy link
Member Author

Ticked SONATA, linboxing, recogbase, automgrp, semigroups.

@olexandr-konovalov
Copy link
Member Author

Need also to check that as many as possible packages with binaries are usable under Windows.

@olexandr-konovalov
Copy link
Member Author

Ticked boxes for liepring, crime, sonata.

@olexandr-konovalov
Copy link
Member Author

Ticked GAPDoc - thanks @frankluebeck.

@fingolfin
Copy link
Member

I will downgrade SmallGrp now, based on the fact that any issues with it are already present in GAP 4.9 anyway, and also because no quick resolution is forthcoming.

Otherwise, I really think we should just release GAP 4.10 now!

@olexandr-konovalov
Copy link
Member Author

I agree. None of the issues with packages above is blocking - a huge progress has been achieved thanks to many, and it will be good to have as many as possible in GAP 4.10.0, but apart from a couple of packages with an imminent new release, we should not wait longer for others. They could go into 4.10.11 or later.

@olexandr-konovalov
Copy link
Member Author

Ticked grape, cryst, curlInterface. Also, new primgrp appeared and will likely make it too.

@olexandr-konovalov
Copy link
Member Author

TIcked primgrp, JupyterViz, SgpViz, simpcomp. I will move the rest of packages to a new issue.

@olexandr-konovalov
Copy link
Member Author

Closing this. See #2984 for monitoring package readiness for GAP 4.11 release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: packages issues or PRs related to package handling, or specific to a package (for packages w/o issue tracker)
Projects
None yet
Development

No branches or pull requests

3 participants