Skip to content

What does a full v2.0.0 release look like? #2803

Description

@goto-bus-stop

I've been publishing alphas for a few years, it would be nice to wrap it up and have a proper thing that we can recommend to people to npm install.

The main things I think so far:

  • Use Typescript for state -- components don't need to be fully ported but at least the reducers. This is partly a cleanliness thing (not calling something that's mid-refactor stable), but also a reliability thing as I still run into crashes somewhat regularly due to values being unexpected shapes or unexpectedly null.
  • Finish the social login feature, we still don't use it on wlk.yt
  • ...do we really need anything else? Many of the things in our issues list can just be point releases.

We likely want to align it with a server 1.0 release. For that I would really like to switch to a SQL database.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions