Again, thanks Max for that! I have created a jira to have a visible place for JBT/Studio efforts to keep track of this.
Adding Fuse tooling team to the loop. Ondrej [1]: https://issues.redhat.com/browse/JBIDE-28286 On Thu, Jan 20, 2022 at 10:31 AM Stephane Bouchet <[email protected]> wrote: > Great, thank you max for this. > I'm looking forward to have some clarification for the future releases of > JbossTools/Codeready studio as we are heavily using Rsync on > filemgmt.jboss.org to make our release available to the public. > > Regards, > > Le jeu. 20 janv. 2022 à 10:23, Max Rydahl Andersen <[email protected]> > a écrit : > >> Hi, >> >> I reached out to the Marks (Newton, Eastman and Little) and are working >> on >> getting some clarifications in place. For now just await an update. >> >> /max >> >> I don't understand why a structure like RH cannot offer such a service >> for the amount of projects requiring such a service. >> >> On Wed, Jan 19, 2022 at 8:08 PM Max Rydahl Andersen <[email protected]> >> wrote: >> >>> Any updates /feedback here ? >>> >>> Are we really saying that it is cheaper to tell countless projects to >>> migrate data to random places, have engineering staff setup and update >>> alternative ci pipelines than maintain a static backed storage ? >>> >>> Any docs on how to retain urls etc. so we don't break users and >>> customers ? >>> >>> /max >>> >>> As i wrote in my first response to this thread i was worrying about it, >>> but now with the latest Mark Newton's msg it is even worse. So we are >>> encouraged to migrate websites completely or active access for uploading to >>> it is discontinued? >>> >>> I think that change would deserve a special email with different topic >>> as it changes what is bringing to us as original msg was nothing changes >>> for projects only the datacenter. >>> Dne 1/16/22 v 18:58 Max Rydahl Andersen napsal(a): >>> >>> On 15 Jan 2022, 17:42 +0100, [email protected], wrote: >>> >>> >>> As such project teams are encouraged to look for alternative hosting >>> providers for any static content they wish to host before then and should >>> take the opportunity to do so before 31st Mar if they want to avoid any >>> unforeseen issues with the filemgmt.jboss.org migration. >>> >>> >>> What does this mean exactly ? That we can’t upload new content via file >>> Mgmt or that the data goes away ? >>> >>> The latter I can’t see as an option as that is where basically all >>> intelli, vscode and eclipse plugins been served out of so it will break >>> tons of active projects. >>> >>> In any case what is the plans to make sure urls used in lots of our >>> tools and ci processes can continue to work after filemgt no longer can be >>> used for upload ? >>> >>> -- >>> Marek Novotny >>> -- >>> >>> RedHat JBoss Middleware >>> >>> Red Hat Czech s.r.o. >>> Purkynova 111 >>> 612 45 Brno >>> >>> >>> /max >>> https://xam.dk/about >>> >> >> >> -- >> >> Jeff Maury >> >> Manager, DevTools >> >> Red Hat EMEA <https://www.redhat.com> >> >> [email protected] >> @RedHat <https://twitter.com/redhat> Red Hat >> <https://www.linkedin.com/company/red-hat> Red Hat >> <https://www.facebook.com/RedHatInc> >> <https://www.redhat.com> >> <https://redhat.com/summit> >> >> >> /max >> https://xam.dk/about >> _______________________________________________ >> Devtools mailing list >> [email protected] >> https://listman.redhat.com/mailman/listinfo/devtools >> > > > -- > > Stéphane Bouchet > > Senior Software Engineer, R&D > > Red Hat <https://www.redhat.com/> > <https://www.redhat.com/> > _______________________________________________ > Devtools mailing list > [email protected] > https://listman.redhat.com/mailman/listinfo/devtools >
_______________________________________________ Devtools mailing list [email protected] https://listman.redhat.com/mailman/listinfo/devtools
