Notice of End of Life for Skeleton v2

[endigo9740]

Hey everyone, Chris here from Skeleton. As we move closer to the upcoming release of Skeleton v3, and alongside today's Release Candidate, we wanted to make it explicitly clear the plans for Skeleton v2 going forward. Let's begin by reviewing what is changing and why.

Release Plans

We've created a diagram to help summarize the changes.

Essentially this means Skeleton v3 will be moved from an unstable pre-release to our active production branch during the v3 release (scheduled for January). At this same time, Skeleton v2 will move from it's current maintenance mode, to being fully archived. For us, archived means there will be no more code changes and no more package releases from that point forward. It will be permanently sunset.

Can I still use Skeleton v2?

Absolutely. Your current installation of v2 will continue to operate as it does now, but will no longer receive updates from that point forward. All NPM packages will remain available - though you may have to specify the version on install. And we'll preserve a backup of the source code on GitHub via a dedicated branch, just like Skeleton v1.

Additionally we will continue to host the v2 documentation, which will follow our standard subdomain pattern:

• https://v1.skeleton.dev/ -> v1 docs archive
• https://v2.skeleton.dev/ -> v2 docs archive (from January and on)
• https://skeleton.dev/ -> v3 production site (from January and on)

NOTE: The next.skeleton.dev website will begin to redirect to the production site until Skeleton v4 begins.

And again, just like our previous transitions, we'll provide a quick link to the older archived versions on the new site:

Why is v2 being archived?

As you may know, we're a small team, which means we don't have the resources or bandwidth to maintain multiples versions in parallel. We actually tried our best to maintain v2 and v3 at the same time this past year, but did eventually shift priorities to focus fully on Skeleton v3. Since then, all contributions to v2 have come directly from the community.

When will this change occur?

As mentioned above, we're slating the Skeleton v3 release for sometime in January. We'll share the exact time and dates once we settle on this over the next few weeks.

What happens to v2 issues on GitHub?

We still have a number of v2 milestone issues. We plan to share this very announcement in each post created by community members. This will provide a final warning that if you wish to see these changes implement to v2, then you should consider contributing your own pull request with said changes asap. Unfortunately the Skeleton team will not have the resources to return to these issues before the v3 launch.

TL;DR - get your final changes in NOW folks! :)

Will any v2 issues move to v3?

In most cases it will not be relevant for v2 issues to carry over to v3. This is due to the fact that most components and features have been rebuilt from the ground up. While they may have new issues to be found and reported, the previous issues are likely no longer relevant. However, in the odd case that something is relevant (a feature request for example) we will consider moving this forward.

Can I migrate from Skeleton v2 to v3?

Yes, our recommendation is to move forward to v3 as soon as you're able post-launch. We've provided a written guide here, and we're actively working on a migration CLI to help automate the process. We anticipate this will drop just before or alongside the v3 launch.

Questions and Feedback

If you have any questions about these changes or would like to provide feedback, please reach out in the comment section below. The team and I are also available via the #skeleton-next channel on Discord.