[Task] Vuetify 3 Release Checklist

[johnleider]

V3 Release Checklist

The following is an in progress list of remaining tasks before we release the next version.

This will be updated daily; so watch for changes.

Discord, https://community.vuetifyjs.com/ and join channel #v3-discussion.

Final review

• [x] Framework Core #15139
• [x] Documentation
• [x] UI Components
• [x] Tooling

Documentation

• [x] Introduction
• [x] Getting started
• [x] Features
• [x] Styles and animations
• [x] Directives
• [x] Resources
• [x] About

Tooling

• [x] CLI plugin
• [x] Vite plugin
• [x] Presets
• [x] Eslint

UI Components

A component is considered complete when the following criteria is met:

* Primary and child components reviewed * imports ordered with appropriate comments * converted to use grid css structure (if applicable) * unit tests * jest spec test (if applicable) * cypress e2e test * SASS/SCSS code reviewed * removes deprecated or unused code * abstracted explicit values to variables * verified sass variable usage * index.ts file export formatted * Documentation page * all examples working with no deprecated code * removed unused or deprecated examples * added **all components** page image * added quick bar and links * updated page entry and formatting * new sections added * accessibility (if applicable) * anatomy * grid (if applicable) * sass variables * theme (if applicable) * updated api section formatting * frontmatter information reviewed

• [x] v-alert #14971
• [x] v-app #15179
• [x] v-app-bar #15192
• [x] v-autocomplete #15355
• [x] v-avatar #15112
• [x] v-badge #15193
• [x] v-banner #15109
• [x] v-bottom-navigation #15194
• [x] v-breadcrumbs #15181
• [x] v-btn #15213
• [x] v-btn-group #15195
• [x] v-btn-toggle #15196
• [x] v-card #15283
• [x] v-carousel #15197
• [x] v-checkbox #15264
• [x] v-chip #14973
• [x] v-chip-group #15198
• [x] v-code #15182
• [x] v-color-picker #15292
• [x] v-combobox #15354
• [x] v-counter #15183
• [x] v-default-provider
• [x] v-dialog #15289
• [x] v-divider #15113
• [x] v-expansion-panels #15295
• [x] v-field #15251
• [x] v-file-input #15288
• [x] v-footer #15114
• [x] v-form #15253
• [x] v-grid #15296
• [x] v-hover
• [x] v-icon #15212
• [x] v-img #15287
• [x] v-input #15260
• [x] v-kbd #15199
• [x] v-label #15256
• [x] v-lazy #15184
• [x] v-list #15360
• [x] v-locale-provider #15255
• [x] v-main #15254
• [x] v-menu 5e4992ffa
• [x] v-messages #15200
• [x] v-navigation-drawer #15263
• [x] v-no-ssr #15185
• [x] v-overlay #15284
• [x] v-pagination #15286
• [x] v-parallax #15226
• [x] v-progress-circular #15266
• [x] v-progress-linear #15265
• [x] v-radio #15258
• [x] v-radio-group #15259
• [x] v-range-slider #15228
• [x] v-rating #15285
• [x] v-responsive #15249
• [x] v-selection-control #15246
• [x] v-selection-control-group #15250
• [x] v-sheet #15115
• [x] v-slide-group #15248
• [x] v-slider #15227
• [x] v-snackbar #15242
• [x] v-switch #15247
• [x] v-system-bar #15243
• [x] v-table #15186
• [x] v-tabs #15262
• [x] v-text-field #15252
• [x] v-textarea #15257
• [x] v-theme-provider
• [x] v-timeline #15230
• [x] v-toolbar #15154
• [x] v-tooltip #15245
• [x] v-validation
• [x] v-window #15244

[genofire]

@johnleider Please keep the issue uptodate and add e.g. v-calender which is makes by @KaelWD (thx): https://github.com/vuetifyjs/vuetify/pull/15038

[johnleider]

can we get any answer instead of marking the comment as outdated??

I would really like to keep giving chance to Vuetify, but by this kind of communication it's even harder to feel reliability of the framework.

Thanks

Reliability of the framework? Give me a break. Take this conversation to Discord and stop whining here.

[johnleider]

@johnleider Please keep the issue uptodate and add e.g. v-calender which is makes by @KaelWD (thx): #15038

It is up to date. v-calendar is not shipping with v3.0.

[MatthewAry]

Here is my unsolicited feedback on this recent tangent, I think others might find it useful. Note: I am making assumptions about the state of things in this project so if I am wrong please feel free to correct me.

@sinisarudan Vuetify 3 is beta, which usually means:

• Development has priority over authoring docs right now.
• Errata, and missing information is to be expected in the docs while in beta up until V3 reaches some unspecified level of maturity.
• The development team has no obligation to provide API guarantees until GA.
• The scope of the V3 initial release is locked in, what you see on the release checklist is meant to give you an idea how close/far they are to release.
• I have my own questions about V3 but I know that it would be inappropriate to ask them HOW to do something with V3 Beta, and more appropriate to ask them if a specific feature, or component will be included in the initial release (excluding anything that they may consider obvious)
• The dev team is free to ignore discussions or bug reports until V3 is released. They are more likely to interact with you if you intend to contribute code or if you engage with them on something that team members are currently concerned with or occupied with.

I specifically posted to this task, because I wanted to know about a feature. I didn't get a response, and it's no big deal for me right now. I have other things to worry about.

TLDR: Don't expect any kind of support from the dev team for non GA releases. They're still making V3 and will more likely converse with you as long as the discussion has to do with any of their present concerns.

[websitevirtuoso]

I think that beta is an incorrect tag for the current situation. It should be alpha. So many components doesn't work properly like they worked in 2.6 version. Everything great. Let's just wait. This is great UI framework. I am still waiting my v-data-table component

[johnleider]

I think that beta is an incorrect tag for the current situation. It should be alpha. So many components doesn't work properly like they worked in 2.6 version. Everything great. Let's just wait. This is great UI framework. I am still waiting my v-data-table component

Which components do not work properly?

[UkonnRa]

I think that beta is an incorrect tag for the current situation. It should be alpha. So many components doesn't work properly like they worked in 2.6 version. Everything great. Let's just wait. This is great UI framework. I am still waiting my v-data-table component

Which components do not work properly?

The Autocomplete in doc is still broken.

[johnleider]

I feel like I shouldn't have to say this since it is plastered on every page of the next docs, but alas:

[websitevirtuoso]

I think that beta is an incorrect tag for the current situation. It should be alpha. So many components doesn't work properly like they worked in 2.6 version. Everything great. Let's just wait. This is great UI framework. I am still waiting my v-data-table component

Which components do not work properly?

Vuetify3 beta3 Component breadcrumbs. Has invalid styles and html structure

Vuetify3 beta3. Validation Error should have red color but it is gray. In beta2. It was red

I sm uding vite and latest version of everything. let me know, I can provide more info. Very appreciate for everything

[MartinX3]

Please learn how to read and stop spamming the Vuetify 3.0 Release CHECKLIST issue ticket.

I didn't subscribe it to read wining people screaming for ETA without really helping the project and ignoring text warnings.

[johnleider]

Would like to suggest adding a Nuxt3 plugin to this list as well.

I will need help with this as I do not use NUXT. Happy to help however I can though.