Apart from releasing the zip archives do we have another option so that the build on the tar.gz does not fail on Windows? I don't remember anybody complaining about this when we were using the maven build, so I am wondering if we had some special configuration.
On Sat, Dec 21, 2019 at 2:44 AM Francis Chuang <[email protected]> wrote: > The broken dockerfiles are really trivial to fix and one of the reasons > I'd like to fix them and release 1.17.0 is so that I can add 1.17.0 as a > test target for Avatica-Go before releasing Avatica-Go 5.0.0. > > In addition to fixing the dockerfiles, we should: > - Agree on whether we need to release a zip archive with source files > encoded using Windows line endings. If we do go down this path, I think > maybe we should add "windows" to the file name of the released > artifacts, so as to not confuse people. > > - Reorder the tasks in publishDist so that the nexus artifacts are > released first before the release is tagged. > > Francis > > On 21/12/2019 6:58 am, Rui Wang wrote: > > 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 <[email protected]> > > 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 < > [email protected]> > >> 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 > >>>> > >>> > >> > > >
