I’d defer back to you; technically you can choose to either way. Think about this: Is it better for community growth to push the release out, or to delay a bit so that an experience on the Windows platform is improved?
The answer probably depends on what portion of the community do you expect to be running on Windows. If your gut feeling is small, you should probably proceed. If significant, you probably should fix it. Either way, it should be fixed for the next release. Also, think when does it make sense to release again. If soon, not a big deal to release as is. If significant, maybe that tips towards fixing it. My gut feeling is: proceed as is, unless more issues are uncovered. If any additional issue get uncovered, fix all of them. (Of course, the next step is IPMC approval.) Happy holidays! Davor On Tue, Dec 25, 2018 at 6:03 PM Byung-Gon Chun <bgc...@gmail.com> wrote: > Mentors, > > We need your advice. > > Thanks! > -Gon > > > On Wed, Dec 26, 2018 at 10:33 AM Joo Yeon Kim <jooy...@apache.org> wrote: > > > Hi all. > > > > I talked with a few others earlier about the Windows test failure, > > and was waiting for a response about what we should do with it. > > > > Is it okay to proceed with the next step? > > > > Best, > > Joo Yeon > > > > On Mon, Dec 24, 2018 at 6:37 AM Byung-Gon Chun <bgc...@gmail.com> wrote: > > > > > Joo Yeon, > > > > > > The last vote was casted a week ago. > > > Could you proceed with the next step? > > > > > > Thanks! > > > -Gon > > > > > > > > > On Mon, Dec 17, 2018 at 2:58 PM Hyunsik Choi <hyun...@apache.org> > wrote: > > > > > > > Hi, > > > > > > > > +1 (binding) > > > > > > > > I verified the signature against KEYS file and MD5, SHA512 digests. I > > > > also tested 'mvn clean install'. > > > > > > > > Best regards, > > > > Hyunsik Choi > > > > On Mon, Dec 10, 2018 at 7:44 PM Joo Yeon Kim <jooy...@apache.org> > > wrote: > > > > > > > > > > Hello Nemo PPMC, > > > > > > > > > > This is a call for the vote to approve the release, 0.1, release > > > > candidate > > > > > 2. > > > > > Since release candidate 1, I have: > > > > > - Excluded examples/beam and examples/spark JARs from the maven > > > artifact > > > > > being published. > > > > > - Added a checkstyle for Apache license headers > > > > > - Removed the platform dependent CRLF character from source tar > ball. > > > > > - Included a few other PRs that have been merged in the meanwhile. > > > > > > > > > > Please refer to the information below to vote on this release, and > > > vote: > > > > > > > > > > [ ] +1 Release this package as Apache Nemo (incubating) 0.1 > > > > > [ ] 0 I don't feel strongly about it, but the release seems okay. > > > > > [ ] -1 Please do not release this package because... > > > > > > > > > > 1. Source release files: > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/nemo/0.1-incubating/ > > > > > > > > > > 2. The release tag: > > > > > * > > > > > > > > > > https://github.com/apache/incubator-nemo/releases/tag/apache-nemo-0.1-incubating-rc2 > > > > > < > > > > > > > > > > https://github.com/apache/incubator-nemo/releases/tag/apache-nemo-0.1-incubating-rc2 > > > > >* > > > > > > > > > > 3. The release hash: > > > > > * > > > > > > > > > > https://github.com/apache/incubator-nemo/commit/3ce6d20fd00f3bed690516abb24475d38edeff16 > > > > > < > > > > > > > > > > https://github.com/apache/incubator-nemo/commit/3ce6d20fd00f3bed690516abb24475d38edeff16 > > > > >* > > > > > > > > > > 4. The Nexus Staging URL: > > > > > * > > > https://repository.apache.org/content/repositories/orgapachenemo-1003/ > > > > > < > > > https://repository.apache.org/content/repositories/orgapachenemo-1003/ > > > > >* > > > > > > > > > > 5. The KEYS file: > > > > > https://dist.apache.org/repos/dist/dev/incubator/nemo/KEYS > > > > > > > > > > > > > > > Best, > > > > > Joo Yeon > > > > > > > > > > > > > -- > > > Byung-Gon Chun > > > > > > > > -- > Byung-Gon Chun >
