Adding the right dev@ list back to the recipients this time...read on below, if you didnt see it elsewhere already ;)
On 13 September 2016 at 22:59, Robbie Gemmell <robbie.gemm...@gmail.com> wrote: > The mirrors just replicate whatever is on the main dist repo. They > take a variable amount of time to update, typically several hours or > more, as they aren't necessarily on the same update period and their > update points are also potentially offset from each other. You can > track mirror ages at https://www.apache.org/mirrors/ > > I tend to wait up to 24hrs or at least until the vast majority of > mirrors have updated after putting new artifacts in for mirroring > before updating the website and actually announcing, unless theres > some need to expedite the notice in which case letting folks know the > mirrors won't yet all be up to date is a good idea. > > Cleaning up old releases once the new release is mirrored rather than > at the same time can be a good idea, otherwise theres a period where > anyone still looking for the existing/old release (still linked from > the not-yet-updated website) may find it want wont be on the mirror > they are using as its updated and only has the new one now (which they > may not know to look for yet). > > Robbie > > On 13 September 2016 at 22:10, Jim Gomes <e.se...@gmail.com> wrote: >> Yes, it'll take some amount of time. Not sure how much. As I was browsing >> manually, I noticed that there are synchronization errors. Most mirrors had >> the 1.3.0 version and not the 1.4.0 version (as expected). However, the >> mirror that I found 1.4.0 on did *not* have 1.3.0. That was surprising. Do >> the mirrors ditch the older version when a newer one comes online? I'm not >> sure how that works. >> >> >> On Tue, Sep 13, 2016 at 2:07 PM Clebert Suconic <clebert.suco...@gmail.com> >> wrote: >> >>> I tested before sending the ANNOUNCE, but I guess not all mirrors have it. >>> >>> I believe it usually takes some time before it syncs them all. I guess >>> that's normal? >>> >>> On Tue, Sep 13, 2016 at 4:55 PM, Jim Gomes <jgo...@apache.org> wrote: >>> > Disregard. There seems to be synchronizing issues between the mirrors. >>> Some >>> > mirrors have it, some don't. I had to manually browse the mirrors to find >>> > one that did. >>> > >>> > On Tue, Sep 13, 2016 at 1:48 PM Jim Gomes <jgo...@apache.org> wrote: >>> > >>> >> The download links are still broken. How long before they will be >>> active? >>> >> >>> >> >>> >> On Tue, Sep 13, 2016 at 8:40 AM Clebert Suconic < >>> clebert.suco...@gmail.com> >>> >> wrote: >>> >> >>> >>> Apache ActiveMQ Artemis 1.4.0 has been released. >>> >>> >>> >>> There are a lot of improvements included in this release: >>> >>> >>> >>> - Possibility of using a max size for paging, and monitoring disk >>> >>> sizes and improving flow control >>> >>> - Interceptors support for MQTT >>> >>> - Reload configuration support >>> >>> >>> >>> The artemis sub-project website has been updated: >>> >>> >>> >>> http://activemq.apache.org/artemis/ >>> >>> >>> >>> >>> >>> >>> >>> For a complete report of changes: >>> >>> >>> >>> >>> >>> >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315920&version=12336052 >>> >>> >>> >>> >>> >>> And the documentation can be found here: >>> >>> >>> >>> https://activemq.apache.org/artemis/docs.html >>> >>> >>> >>> >>> >>> >>> >>> Regards >>> >>> >>> >>> >>> >>> >>> >>> Clebert Suconic >>> >>> >>> >> >>> >>> >>> >>> -- >>> Clebert Suconic >>>
