SilverBullet v2: The Path Forward

Announcements
12

Update

  • I’ve now replaced the main branch with the v2 branch. So v2 now is the main line of development. I’ve created a v1 branch for further 0.x maintenance.
  • I’ve switched over https://silverbullet.md to v2 as well, the old website now lives at https://v1.silverbullet.md
  • Docker images for v2 are still pushed only to :v2 until I’m ready for a “full proper release”. The install instructions website tells you to use :v2 now, though.

What this should not have affected:

  • the :edge Docker images are no longer updated, and frozen where they were ~11 days ago
  • The :latest Docker image is also untouched
  • Both of these will still give you 0.x releases

So no “magic” upgrade should happen for anybody who did not explicitly opt into v2 earlier. However, new people arriving to https://silverbullet.md will now simply onboard to v2.

Non-docker (so “pure Deno”) installations will return. I just need to figure out how to properly do this. Until then, I’ve removed instructions from the website.

The website content, while not complete should now at least reflect SilverBullet v2 and its feature set as it exists today. I’ve removed documentation for features that are gone, or have not yet been been brought back.

10 Likes