The issue with java documentation is resolved after opening https://issues.apache.org/jira/browse/INFRA-14117. Now java doc for 3.6.0 is available at https://ci.apache.org/projects/apex-core/apex-core-javadoc-release-3.6/index.html
- Tushar. On Mon, May 8, 2017 at 11:11 AM, Tushar Gosavi <tus...@datatorrent.com> wrote: > I have updated https://svn.apache.org/repos/infra/ > infrastructure/buildbot/aegis/buildmaster/master1/projects/apex.conf file > by adding release-3.6 branch for Apex Core. For some reason builder is not > registered for release-3.6 and force build through IRC is also not working > as builder is not registered. > > I am communicating through IRC for the resolution of the issue. No > response till now. I may open an INRA JIRA for it. > > Regards, > -Tushar. > > > On Sat, May 6, 2017 at 10:23 PM, Thomas Weise <t...@apache.org> wrote: > >> The javadocs are not pushed yet. >> >> https://ci.apache.org/projects/apex-core/apex-core-javadoc- >> release-3.6/index.html >> >> Last time, Ram had to trigger buildbot manually to make it happen. >> >> Ram, what is the magic to do that? We should also document it in case the >> trigger on commit or nightly build does not happen. >> >> >> >> On Fri, May 5, 2017 at 6:41 AM, Thomas Weise <t...@apache.org> wrote: >> >> > Move of RC to release is done and new JIRA version added. >> > >> > >> > On Fri, May 5, 2017 at 6:34 AM, Vlad Rozov <v.ro...@datatorrent.com> >> > wrote: >> > >> >> I'll help with moving RC candidate from dev to release. Do you have >> >> permission to publish artifacts to maven? >> >> >> >> Thank you, >> >> >> >> Vlad >> >> >> >> On 5/5/17 06:21, Thomas Weise wrote: >> >> >> >>> You should be able to complete the release activities except the JIRA >> >>> version. What do you mean by "release svn repository"? >> >>> >> >>> Also, release process states that you should turn off JIRA >> notifications >> >>> when closing issues (to not flood mailing list). >> >>> >> >>> Subject of closing vote should start with [RESULT] >> >>> >> >>> Yes, the semantic versioning check should be updated for both >> branches. >> >>> >> >>> Thomas >> >>> >> >>> >> >>> On Fri, May 5, 2017 at 2:34 AM, Tushar Gosavi <tus...@datatorrent.com >> > >> >>> wrote: >> >>> >> >>> As a committer, I do not have write permissions to release svn >> >>>> repository. >> >>>> Need help from PMC member to update the release repository. Any >> >>>> volunteers?? >> >>>> >> >>>> Also one more clarification needed with respect to updating semantic >> >>>> versioning check. Does it needs to be done for both release-3.6.0 and >> >>>> master branch? >> >>>> >> >>>> I will push the documentations after release repository is updated. >> >>>> >> >>>> Thanks, >> >>>> -Tushar. >> >>>> >> >>>> >> >>>> On Fri, May 5, 2017 at 11:35 AM, Tushar Gosavi < >> tus...@datatorrent.com> >> >>>> wrote: >> >>>> >> >>>> The vote is concluded and passes. Thanks everyone for voting and >> >>>>> >> >>>> verifying >> >>>> >> >>>>> the release. >> >>>>> >> >>>>> binding +1 (4) >> >>>>> >> >>>>> Vlad Rozov >> >>>>> Thomas Weise >> >>>>> Amol Kekre >> >>>>> Pramod Immaneni >> >>>>> >> >>>>> >> >>>>> non-binding +1 (2) >> >>>>> Bhupesh Chawda >> >>>>> Chaitanya Chebolu >> >>>>> >> >>>>> No other votes. >> >>>>> >> >>>>> Will complete the release activities. >> >>>>> >> >>>>> Thanks, >> >>>>> Tushar. >> >>>>> >> >>>>> >> >>>>> On Thu, May 4, 2017 at 12:05 PM, Chaitanya Chebolu < >> >>>>> chaita...@datatorrent.com> wrote: >> >>>>> >> >>>>> +1 >> >>>>>> >> >>>>>> 1) Verified the file Integrity check. >> >>>>>> 2) Verified the source code using tar file. >> >>>>>> - Extracted tar file and compiled. >> >>>>>> - No binary files >> >>>>>> - LICENSE, NOTICE, README, CHANGELOG.md exist. >> >>>>>> - rat check >> >>>>>> 3) Launched PI demo. >> >>>>>> >> >>>>>> Regards, >> >>>>>> Chaitanya >> >>>>>> >> >>>>>> On Wed, May 3, 2017 at 7:07 AM, Pramod Immaneni < >> >>>>>> pra...@datatorrent.com >> >>>>>> wrote: >> >>>>>> >> >>>>>> +1 (binding) >> >>>>>>> >> >>>>>>> verified file integrity >> >>>>>>> no unexpected binary files >> >>>>>>> existence of README.md, NOTICE, LICENSE and CHANGELOG.md files >> >>>>>>> checked build and licenses >> >>>>>>> launched and ran pi demo >> >>>>>>> >> >>>>>>> Minor nitpicks >> >>>>>>> >> >>>>>>> CHANGELOG.md has a line in the beginning of the file that has a >> date >> >>>>>>> >> >>>>>> in >> >>>> >> >>>>> future "Version 3.6.0 - 2017-05-04" >> >>>>>>> Please have your key signed by some of the others in the KEYS >> file, >> >>>>>>> >> >>>>>> right >> >>>>>> >> >>>>>>> now it is self-signed >> >>>>>>> >> >>>>>>> Thanks >> >>>>>>> >> >>>>>>> On Mon, May 1, 2017 at 11:49 AM, Tushar Gosavi < >> >>>>>>> >> >>>>>> tus...@datatorrent.com> >> >>>> >> >>>>> wrote: >> >>>>>>> >> >>>>>>> Dear Community, >> >>>>>>>> >> >>>>>>>> Please vote on the following Apache Apex Core 3.6.0 release >> >>>>>>>> >> >>>>>>> candidate >> >>>> >> >>>>> 1. >> >>>>>> >> >>>>>>> This release adds the support for custom control tuples, >> >>>>>>>> >> >>>>>>> experimental >> >>>> >> >>>>> support for plugins >> >>>>>>>> and other improvements and important bug fixes. >> >>>>>>>> >> >>>>>>>> This is a source release with binary artifacts published to >> Maven. >> >>>>>>>> >> >>>>>>>> List of all issues fixed: https://s.apache.org/HQ0r >> >>>>>>>> >> >>>>>>>> Staging directory >> >>>>>>>> https://dist.apache.org/repos/dist/dev/apex/apache-apex-core >> >>>>>>>> >> >>>>>>> -3.6.0-RC1/ >> >>>>>> >> >>>>>>> Source zip: >> >>>>>>>> https://dist.apache.org/repos/dist/dev/apex/apache-apex- >> >>>>>>>> core-3.6.0-RC1/apache-apex-core-3.6.0-source-release.zip >> >>>>>>>> Source tar.gz: >> >>>>>>>> https://dist.apache.org/repos/dist/dev/apex/apache-apex- >> >>>>>>>> core-3.6.0-RC1/apache-apex-core-3.6.0-source-release.tar.gz >> >>>>>>>> Maven staging repository: >> >>>>>>>> https://repository.apache.org/content/repositories/ >> >>>>>>>> >> >>>>>>> orgapacheapex-1028 >> >>>> >> >>>>> Git source: >> >>>>>>>> https://git-wip-us.apache.org/repos/asf?p=apex-core.git;a= >> >>>>>>>> commit;h=refs/tags/v3.6.0-RC1 >> >>>>>>>> (commit: 5a517348ae497c06150f32ce39b6915588e92510) >> >>>>>>>> >> >>>>>>>> PGP key: >> >>>>>>>> http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=tushar@ >> >>>>>>>> >> >>>>>>> apache.org >> >>>>>> >> >>>>>>> KEYS file: >> >>>>>>>> https://dist.apache.org/repos/dist/release/apex/KEYS >> >>>>>>>> >> >>>>>>>> More information at: >> >>>>>>>> http://apex.apache.org >> >>>>>>>> >> >>>>>>>> Please try the release and vote; vote will be open for at least >> 72 >> >>>>>>>> >> >>>>>>> hours. >> >>>>>> >> >>>>>>> [ ] +1 approve (and what verification was done) >> >>>>>>>> [ ] -1 disapprove (and reason why) >> >>>>>>>> >> >>>>>>>> http://www.apache.org/foundation/voting.html >> >>>>>>>> >> >>>>>>>> How to verify release candidate: >> >>>>>>>> >> >>>>>>>> http://apex.apache.org/verification.html >> >>>>>>>> >> >>>>>>>> Thanks, >> >>>>>>>> Tushar. >> >>>>>>>> >> >>>>>>>> >> >>>>>> >> >>>>>> -- >> >>>>>> >> >>>>>> *Chaitanya* >> >>>>>> >> >>>>>> Software Engineer >> >>>>>> >> >>>>>> E: chaita...@datatorrent.com | Twitter: @chaithu1403 >> >>>>>> >> >>>>>> www.datatorrent.com | apex.apache.org >> >>>>>> >> >>>>>> >> >>>>> >> >> >> > >> > >
