I just wanted to update the community on my progress pushing out the new release candidate. I was able to successfully regenerate ALL of the sdist/bdist/doc artifacts and they are currently sitting at apache's svn public area for aria as before. They images are signed, and the key info is there as well.
I am missing only 1 thing now: pushing the candidate artifacts to pypi's "testing" staging area with twine. Im blocked now because one needs the login credentials for pypi.org. Does anyone know the credentials for pypi.org? We need the ariatosca account's information. I don't believe I can just create a personal account and push there. I cannot push the 0.2.0 candidates there until I get the info. BTW please unicast me on slack or email with the credentials - please DO NOT reply-all here. 8) Cheers, --Tom On Fri, Dec 29, 2017 at 8:31 PM, Tal Liron <[email protected]> wrote: > Thanks, Jakob. I am changing my vote to: -1. > > On Fri, Dec 29, 2017 at 4:42 PM, Jakob Homan <[email protected]> wrote: > > > -1 (binding) > > > > * The release needs to be signed, include the signature and sha512 and > > md5 hashes (see > > https://dist.apache.org/repos/dist/dev/incubator/airflow/1.9.0rc8/ for > > an example) > > * Copyright in NOTICE should just be 2017 rather than range > > > > * NOTICE/DISCLAIMER/LICENSE look good > > * Headers look good > > * Didn't see any included libraries that would require inclusion in > LICENSE > > > > Also, just to clarify on the voting procedure. The entire community > > is encouraged to vote on releases, although on the Podling Project > > Management Committee (PPMC) has binding votes. Testing and voting on > > releases is an excellent way to contribute to project. > > > > -Jakob > > > > On 28 December 2017 at 07:15, Thomas Nadeau <[email protected]> > wrote: > > > I forgot to vote myself. I downloaded and unpacked the release, the > > > version number there appeared correct, the API docs are in the package, > > > installs correctly using 'make install-virtual', all tests run with > "make > > > test" as well. > > > > > > --Tom > > > > > > > > > On Wed, Dec 27, 2017 at 10:49 AM, Tal Liron <[email protected]> wrote: > > > > > >> +1 > > >> > > >> - I downloaded and unpacked the release. > > >> - Version is correct. > > >> - API docs are in "docs/html". > > >> - All tests run with "make test". > > >> - Installs correctly with "make install-virtual". > > >> - Played around with Clearwater example. > > >> > > >> > > >> On Tue, Dec 26, 2017 at 10:11 AM, Thomas Nadeau < > [email protected]> > > >> wrote: > > >> > > >> > Aria Community: > > >> > > > >> > This is a vote to release Apache AriaTosca (Incubating) 0.2.0. If > the > > >> vote > > >> > passes, another vote for approving the release will take place on > the > > >> > Apache Incubator's PMC. > > >> > > > >> > I created a tarball candidate for the 0.2.0 release and placed it in > > >> ARIA's > > >> > /dist/dev folder: > > >> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/ > > >> > 0.2.0-candidate/ > > >> > The list of issues Resolved for this release are simply all the > issues > > >> that > > >> > have been resolved thus far since the last release. Those can be > found > > >> > here: > > >> > https://issues.apache.org/jira/secure/RapidBoard.jspa? > > >> > rapidView=150&projectKey=ARIA&view=planning&selectedIssue=ARIA-394 > > >> > Instructions for installation etc. may be found in the README file > > inside > > >> > the tarball. Please vote to publish this tarball on ARIA's > > /dist/release > > >> > folder. The voting for this as I understand it, must be open for 3 > > full > > >> > days to all Committers within the project, and then for 3 full days > on > > >> the > > >> > Apache PMC. Voting for the release will begin now at 12PM EST, > > Tuesday, > > >> > December 26, 2017 and be completed on 12PM EST on Friday, December > > 29, > > >> > 2017. > > >> > > > >> > Thanks, > > >> > > > >> > --Tom > > >> > > > >> > > >
