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

v0.3.0 (final release before moving to Django) #197

Closed
wants to merge 64 commits into from
Closed

v0.3.0 (final release before moving to Django) #197

wants to merge 64 commits into from

Conversation

pirate
Copy link
Member

@pirate pirate commented Mar 27, 2019

The v0.3.0 Release

A bunch of big changes:

  • entire codebase is now mypy type-checked, with runtime type enforcement so that a bug doesn't lead to malformed indexes being written to disk
  • all disk writes are now atomic so that power loss / SIGTERM during execution doesn't leave the index in an inconsistent state (as long as the archive folder is on a local, non-network filesystem)
  • core data model now uses typed, immutable dataclasses instead of plain dicts
  • schema and json loading and parsing are formalized all in one place schema.py (laying the foundations for a future transition to Django models)
  • got rid of all derivable redundant data in the index files
  • Much faster performance when passing over old links by avoiding excessive index writes
  • Entirely new UI for the Index Details page:

Screen Shot 2019-03-27 at 3 49 46 AM

@noqqe
Copy link

noqqe commented Apr 2, 2019

cant wait to see this in master! 😍

@pirate pirate changed the title v0.3.0 v0.3.0 (last release before moving to Django) Apr 2, 2019
@pirate pirate changed the title v0.3.0 (last release before moving to Django) v0.3.0 (final release before moving to Django) Apr 2, 2019
@pirate
Copy link
Member Author

pirate commented Apr 3, 2019

FYI for people following this PR, the next release after this PR is also up already: #207

The plan is to release both versions (nearly) simultaneously. Users that want to stay on the stable pre-django version can use v0.3.0, and users who want the latest cutting-edge release can install v0.4.0 and enjoy the new CLI experience.

@pirate
Copy link
Member Author

pirate commented Apr 22, 2019

Ok I think this is done, I'm going to close this PR and recommend everyone upgrade straight to v0.4.0 when it's released (unless you have a specific reason to use this version).

@pirate pirate closed this Apr 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants