Hi all, cc @Daan, @Sven, @Rohit, and @David. Thank you for your responses to my ideas. 1. As far as I know, Vue3 is still being developed and after a few experiments in Cloudstack, I found that it works quite stably 2. The release frequency of the new version is usually monthly. I'm using version 3.1and the latest one is 3.2. 3. From what I experimented with in my draft PR, the conversion accounts for about 60% to 70% and the support from the community is pretty helpful. In case I get any problems, I will definitely get in touch. 4. I think the duration of 1 month would be enough. 5. Also completing it according to 4.17 milestones is totally feasible.
Thanks & Regards. On 2021/09/09 20:28:28, Sven Vogel <s.vo...@ewerk.com> wrote: > Hi Hoang, > > Interesting PR and it Sound like a good plan. > > Cheers > > Sven > > __ > > Sven Vogel > Senior Manager Research and Development - Cloud and Infrastructure > > EWERK DIGITAL GmbH > Br?hl 24, D-04109 Leipzig > P +49 341 42649 - 99 > F +49 341 42649 - 98 > s.vo...@ewerk.com > www.ewerk.com > > Gesch?ftsf?hrer: > Dr. Erik Wende, Hendrik Schubert, Tassilo M?schke > Registergericht: Leipzig HRB 9065 > > Support: > +49 341 42649 555 > > Zertifiziert nach: > ISO/IEC 27001:2013 > DIN EN ISO 9001:2015 > DIN ISO/IEC 20000-1:2018 > > ISAE 3402 Typ II Assessed > > EWERK-Blog<https://blog.ewerk.com/> | > LinkedIn<https://www.linkedin.com/company/ewerk-group> | > Xing<https://www.xing.com/company/ewerk> | > Twitter<https://twitter.com/EWERK_Group> | > Facebook<https://de-de.facebook.com/EWERK.Group/> > > > Ausk?nfte und Angebote per Mail sind freibleibend und unverbindlich. > > Disclaimer Privacy: > Der Inhalt dieser E-Mail (einschlie?lich etwaiger beigef?gter Dateien) ist > vertraulich und nur f?r den Empf?nger bestimmt. Sollten Sie nicht der > bestimmungsgem??e Empf?nger sein, ist Ihnen jegliche Offenlegung, > Vervielf?ltigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte > informieren Sie in diesem Fall unverz?glich den Absender und l?schen Sie die > E-Mail (einschlie?lich etwaiger beigef?gter Dateien) von Ihrem System. Vielen > Dank. > > The contents of this e-mail (including any attachments) are confidential and > may be legally privileged. If you are not the intended recipient of this > e-mail, any disclosure, copying, distribution or use of its contents is > strictly prohibited, and you should please notify the sender immediately and > then delete it (including any attachments) from your system. Thank you. > > ________________________________ > Von: Rohit Yadav <rohit.ya...@shapeblue.com> > Gesendet: Thursday, September 9, 2021 2:40:29 PM > An: dev@cloudstack.apache.org <dev@cloudstack.apache.org> > Betreff: Re: [DISCUSS] Upgrade to Vue3 library > > +1 > > I think it's good idea if Vue and Antd are going to cease support for current > dependencies sometime in future. Based on VueJS's roadmap board looks like > they're going to support the last 2.7 release + then support if for next 18 > months. > > Based on your current work-in-progress PR, it looks like you've the > initiative under control - let us know what kind of timeline/effort you would > require and assistance from community in terms of QA/testing? > > +1 to what David suggests, the sooner we get it into main towards 4.17 > milestone, we've at least 3-5months to stabilises the UI (for any > regressions/issues). > > > Regards. > > ________________________________ > From: David Jumani <david.jum...@shapeblue.com> > Sent: Thursday, September 9, 2021 16:46 > To: dev@cloudstack.apache.org <dev@cloudstack.apache.org> > Subject: Re: [DISCUSS] Upgrade to Vue3 library > > Hi Hoang, > > I like the idea of migrating to Vue 3 which will eventually be needed, and in > my opinion, the sooner the better :) > > I had a look at the migration guide as well as the breaking changes and so I > have a few things on which I'd like clarity : > 1. I see that Vue3 is still being developed, so how is the stability ? > 2. How is the vue release cycle and which 3.x version are we targetting ? > 3. There are significant changes in some components and I see that you've > already created a draft PR, So will you be taking charge of the migration and > would you require any assistance from the community ? > 4. What would be the timeline required to complete it ? > 5. If it can be done relatively quickly, say within a month, would it make > sense to target it for 4.17 or if it would take longer to target a further > release ? (I'd like there to be sufficient time to thoroughly test prior to a > release) > > Thanks, > David > ________________________________ > From: Nguyen Mai Hoang <hoan...@apache.org> > Sent: Tuesday, September 7, 2021 6:19 AM > To: dev@cloudstack.apache.org <dev@cloudstack.apache.org> > Subject: [DISCUSS] Upgrade to Vue3 library > > Hi All, > > We are upgrading a Vue 2 application to Vue 3 on CloudStack. As far as our > investigation goes, Vue 3 does support migration from Vue 2 to Vue 3 by using > `@vue/compat` (aka "the migration build"). However, it is worth mentioning > that there are some incompatible features (please refer to: > https://v3.vuejs.org/guide/migration/migration-build.html#overview). > The biggest differences between Vue 2 and Vue 3 on Cloudstack are: > - mount: https://v3.vuejs.org/guide/migration/mount-changes.html#overview > - Slots: https://v3.vuejs.org/guide/component-slots.html#slots > - Async components: > https://v3.vuejs.org/guide/migration/async-components.html#async-components > - Events: https://v3.vuejs.org/guide/migration/events-api.html#overview > - Watch: https://v3.vuejs.org/guide/migration/watch.html#overview > > In order to make them compatible with Vue 3, it is necessary to upgrade or > replace some libraries as well as some other components, which are listed > below: > - Antd: https://2x.antdv.com/components/overview > - Router: https://next.router.vuejs.org/installation.html > - I18n: https://vue-i18n.intlify.dev/introduction.html > - Clipboard: https://www.npmjs.com/package/vue3-clipboard > - Vue-ls (https://www.npmjs.com/package/vue-ls) => vue-web-storage > (https://github.com/ankurk91/vue-web-storage) > > These upgrades and replacements will require changes in source code, > structure and elements in UI. We would like to have your opinions about it. > > Thank you and best regards, > > > > > > >
