Official release

[anrolmar]

Edit (from @VividLemon): Review #1722 (comment) for official release information

Hi, everyone.

Do you know when we could have an oficial release? I mean the version 1.X

I cannot see anything about this on the Projects tab

[xvaara]

We still have a few "big" issues: https://github.com/orgs/bootstrap-vue-next/projects/1

And we're busy with real work and life, so not that much time to donate to open source.

[VividLemon]

Prologue:

I've seen many questions about the state of the lib and if they "should" use it in production. I can't really speak about whether or not someone should do it, but from experience, most features exist and people can usually use things without issue. Assuming the components one needs have not been neglected. Generally though, most components are in a ready-enough state to be usable. If various features or bugs are found, the author of the issue would probably find most utility in fixing the issue themselves.

The official position on the road to v1:

What I have been working on and need to do:
Most of the work that I have been doing in recent times has been infrastructural. Such as adding auto-import for directives for the nuxt module.
Given this, there is a few things I am personally working on. Such as:

1. Implement aliasing system #1753
2. Global options #1607
   These two are the biggest issues of mine. And they should be left to me as they require some large scale changes. (Note: I've been busy with work. Coincidentally I've been also upgrading a project to Vue 3. Which I agree, takes a significant amount of time)

Now the list of things that I am not working on that need to be finished:

1. There needs to be a parity list. Information here Generate a parity list report #1775
2. Removal of Booleanish type globally. Information here Remove Booleanish type. Replace with boolean #1774 (This is the only remaining breaking change I can think of atm)
3. Expansion of utility props. Information Adding attrs and class props for items that need it #1776
4. Re-evaluation of slots. Information Re-evaluate slots and their roles #1777

Once we have a parity list, the goal of that is to implement the missing functionality. (Note: not everything will be implemented, we just need it documented about what is not going to be implemented).

Finally, after implementing the missing functionality, the documentation needs to be updated and fixed. Information #1778

Naturally, in combination with the parity list, a migration guide needs to be created using the data from the parity list

Note: finalization of any of the final steps (implementing parity features & documentation) is not a blocking value. These final steps can be labelled as a release candidate version

[VividLemon]

@VividLemon Thanks for the comment, I was looking for some source about the "production-readiness", so not so much about missing features but more about "can the lib be used in production without critical bugs or security issues?". Global options would be great but aren't a blocker to use the lib in production imho. Is there an issue on this? Did some search but haven't found any, so I thought I ask here.

If you are asking me, I cannot make that decision. If I could make that decision, v1 would have been announced. And when I can make this decision, v1 will be announced.

However, I find most people find that things are functional and work without much issue.

Really, the biggest blocker on v1 is #1775 . It is a necessity for 1: addressing which things have not been implemented and what needs to be done and 2: creating a migration guide. But, given that, we can see the finish line.

[VividLemon]

I'd say that the lib is in a "release candidate" version. The remaining issues are mostly compatibility fixes