start work on new Rogue Scholar API #876
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I will first retire the current frontend (https://rogue-scholar-org) before Christmas (December 15). The API will stay around longer, as there is a bit of work around integrating existing functionalities (metadata extraction from RSS, DOI registration, PDF generation). My current guess is to keep the current API running until end of June 2025. |
maelle
force-pushed
the
new-rogue-scholar-api
branch
from
07d5352 to
d689a7b
Compare
maelle
force-pushed
the
new-rogue-scholar-api
branch
from
3610aed to
b3137cd
Compare
|
for the record this is building locally 🫠 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #872
@mfenner when exactly will you pull the plug on the current production API?