Is Fluent 9 dying ? #33976
-
|
Is fluent 9 entering maintenance mode, what are the plans for it? Over the last year it seems to have lost traction completely. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments
-
|
Hey thanks for asking @kevinfairclough, I'd say it's very much not dying! We have over the last year reached component parity with the Fluent v8 library, so it's completely expected that you won't see new component releases. We are still very much committed to the library and making improvements, even if they don't come in the form of new features. Is there something in particular that makes it seem like the project is dying? Thanks again for the feedback! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, that's good to hear. It was mainly stuff hanging around in Preview Components for a while such as Virtualizer, the introduction of contributors packages and a lot of feature requests not being triaged i.e. those relating to Combobox and Picker stories as well as outstanding issues list in GitHub. Do you know the LTS plans for Fluent 9 ? Many Thanks |
Beta Was this translation helpful? Give feedback.
-
|
Hey @kevinfairclough , as @JustSlone mentioned above, v9 is very much not dying, quite the opposite! Just a bit of extra information about preview components: they can definitely be used in production already and for this reason specifically, we're always keeping them within our npm package for backwards compatibility, even though most users prefer to switch to stable, once a component gets there. Regarding Virtualizer and other components (ColorPicker, Nav, KeyTips and Motion), the goal is to have them all released to stable by mid next month. There's a lot of work that was put into these components and we always go through a thorough validation process before releasing a component to stable. The validation process is proportional to the component's project usage, so that's why for some of them it can take longer to reach the stable milestone. Nonetheless, as I mentioned above, once a component reaches the Preview state it's considered as ready for use, although breaking changes can be expected during this stage. Regarding triaging, we also have a well defined process that we go through each week where the goal is to have 0 untriaged issues by the end of the week. In our case "triaged" means acknowledged and assigned to the right owner. We're also trying to improve our soft-closing process, by trying to at least give clear answer on feature requests whether they will be planned or not. The creation of fluentui-contrib was organic, as we decided that that would be the right place for higher level abstractions / utilities built on top of our components, which are atomic, primitive components by design. Nonetheless, we tried our best to make that part of our ecosystem as discoverable and sharing the same DX principles as the core repository. Our plan for v9 is to keep doing fixes and add incremental features as long as possible, for a minimum of 2-5 years. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the clarification. Please take a look at the React 19 request we have put in earlier. It would help very much to be able to upgrade to React 19. |
Beta Was this translation helpful? Give feedback.
-
|
Many thanks for the replies |
Beta Was this translation helpful? Give feedback.
Hey thanks for asking @kevinfairclough, I'd say it's very much not dying!
We have over the last year reached component parity with the Fluent v8 library, so it's completely expected that you won't see new component releases. We are still very much committed to the library and making improvements, even if they don't come in the form of new features.
Is there something in particular that makes it seem like the project is dying? Thanks again for the feedback!