As a PMC, we think we need to better document our "+1"s than "Everything seems fine."
For example: Did you check the ASC, MD5 and SHA1 files? _How_ exactly does it "seem" fine? What JDK(s) did you use to build? What did you build? From what? The tag? The zip? And so on. Gary On Sun, Jul 16, 2017 at 12:04 PM, Mikael Ståldal <[email protected]> wrote: > +1 > > Everything seems fine. > > > > On 2017-07-16 18:41, Matt Sicker wrote: > >> Hello all, sorry for the delay between release candidates. This is a vote >> to release RC2 of Log4j Scala API 11.0, the first release of the new >> repository. The main features in this release are Scala 2.12 support and >> an >> API for manipulating the ThreadContext. >> >> Artifacts are available in this staging repository: < >> https://repository.apache.org/content/repositories/orgapachelogging-1028/ >> >. >> The site is on <https://rgoers.github.io/log4j-scala-site/> (though it's >> not appearing for me at the time of writing). Don't mind the styling >> issues >> in component pages as these will point to the correct paths when merged >> with the existing site. >> >> The artifacts are signed with my GPG key with the >> ID 748F15B2CF9BA8F024155E6ED7C92B70FA1C814D which is available in the >> Logging KEYS file. >> >> Artifacts can be downloaded using the following command: >> >> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate >> https://repository.apache.org/content/repositories/orgapache >> logging-1028/org/apache/logging/log4j/ >> >> If that doesn't work, please let me know so I can note the correct command >> for future vote emails. >> >> >
