On Wed, 17 Jun 2020, 21:21 Matthias Bläsing, <[email protected]> wrote:
> I would not use an extra "dev" version, as that will most probably just > rot. > Yes, dev as synonym for next for plugins (not updates) always pointing to the next release would be great. Having /dev for plugins handled at the plugin portal end simplifies the redirects. I assume, that we'd retain the proxy for the 8.2 update center unless > oracle decommissions the old server? > I guess. Removing it for 12.0 was -1'd. It's separate from the standard templated UC and plugin links anyway. > > We could also just proxy those links from those places without > > redirect? Might help with issue of being blocked when processing a > > lot of updates? > > This I don't understand. > Sorry! If you try to use the Ant build support, say, for downloading the platform (via nbms), you'll get blocked by ASF infrastructure before it completes. This works fine if using the VM link or downloads.a.o directly. Trying to install a whole cluster via IDE may also be problematic - something to test. This might be something we could use the ousol mirrors for. These are > explicit mirrors, so bandwidth is either allocated to them or spare > bandwith is used. > Maybe. The bandwidth usage will be minimal - probably more to mirror the nightly build in the first place, given the catalog is almost the only thing that will be downloaded. Is it worth the effort / complexity to implement? Best wishes, Neil
