I am less familiar with the broken docker stuff. Depending on how people think about it: If it is not a big problem, one thing could be done is to include it into the release notes with a section that mentions it (I have seen such practice before).
-Rui On Fri, Dec 20, 2019 at 8:53 AM Stamatis Zampetakis <zabe...@gmail.com> wrote: > First of all many thanks Francis for the release of 1.16.0. Being at the > same time RM, contributor, and beta tester of the Gradle release build was > definitely not easy :) > Also special thanks to Vladimir who spend a lot of time polishing the new > build system and helping in the resolution of the various problems. > Last but not least, many thanks to all contributors of the 1.16.0, great > work! > > Regarding the docker hub links, personally I don't find it a huge problem > since people can still obtain and use the new release by other means. > Having said that, I wouldn't mind having a 1.17.0 with the fix for docker. > We could also take advantage of this, to decide if we want to do something > for the build problem of the artifacts in Windows systems. > > Best, > Stamatis > > > On Thu, Dec 19, 2019 at 11:28 PM Francis Chuang <francischu...@apache.org> > wrote: > > > From past experience, I think it the files should become available as > > long as the repository is marked as released within nexus, so this > > shouldn't be too much of a problem. > > > > On 20/12/2019 9:18 am, Vladimir Sitnikov wrote: > > > AFAIK it does wait for the Nexus to release, however, I have no idea if > > > that means the files are immediately available. > > > > > > Vladimir > > > > > >
