Thanks! On Mon, Jun 4, 2018 at 1:31 PM, Dave Fisher <dave2w...@comcast.net> wrote:
> Hi Herons, > > Your Mentors should be available to answer these type of release > questions. You need to ask these straight up on the dev@heron mailing > list and not go to people within one of the companies working on related > projects. The Incubator has additional rules beyond Apache’s Release Policy > [1] > > Typically you would put [MENTORS] at the beginning of the subject. Justin > Mclean gave a talk at Apachecon NA last year. [2] > > Do you all understand? If it doesn’t happen on the mailing list it didn’t > happen is for a reason. > > I also suggest that if you are going to continue these sync ups that you > provide an agenda at least 24 hours in advance. This can actually serve as > calls for discussion. It is important to do this. You might find that your > questions will be answered before the “sync up” by participating in the > global asynchronous advantage of emails! > > Please think about this! > > Regards, > Dave > > [1] https://incubator.apache.org/guides/releasemanagement.html > [2] https://www.youtube.com/watch?v=I0-lp1t9ee0 > > > On May 22, 2018, at 11:22 PM, Ning Wang <wangnin...@gmail.com> wrote: > > Regarding the Apache release. Sijie responded with the following valuable > information: > > The general guideline of release: > http://www.apache.org/dev/release-publishing.html > An example release process (bookkeeper): > http://bookkeeper.apache.org/community/release_guide/ > > For heron release, I think you need to take care of following 3 parts: > - For java artifacts (e.g heron api), you need to publish the java > artifacts to apache artifactory. So you need to enable Nexus access for > heron. File a JIRA to INFRA - example: [INFRA-14694 Enable Nexus Access For > Pulsar - ASF JIRA](https://issues.apache.org/jira/browse/INFRA-14694) > - You need to have a location on apache dist to host those src/binary > packages. File a JIRA to INFA - example: [INFRA-13024 Setup dists for > Apache DistributedLog - ASF JIRA]( > https://issues.apache.org/jira/browse/INFRA-13024) > - website/documentation. That’s not related to releases, but you > eventually need to put the content under http://heron.incubator.apache. > org/ > , which you need to enable gitpubsub. So when you put the generated website > content under `asf-site` branch, the website is automatically published to > http://heron.incubator.apache.org/ . File a JIRA to INFRA - example: > [INFRA-14587 Enable Gitpubsub for Apache Pulsar (incubating) - ASF JIRA]( > https://issues.apache.org/jira/browse/INFRA-14587) > > > Here are the Apache Infra tickets I just created accordingly: > Nexus access: https://issues.apache.org/jira/browse/INFRA-16560 > Dists: https://issues.apache.org/jira/browse/INFRA-16561 > gitpubsub: https://issues.apache.org/jira/browse/INFRA-16562 > > Please feel free to comment if I missed anything or there is any mistakes. > > > > > > > > > On Tue, May 22, 2018 at 3:20 PM, Ning Wang <wangnin...@gmail.com> wrote: > > Brief notes: > > > > > > * - Not much progress in the new release so far. Twitter forks will reach > out to Bill/Sijie for suggestions.- Productionize stateful process in > Twitter. Found an issue with local checkpoint expiration. - Downloader has > been refactored to be more flexible. - Discussed zombie aurora container > (causing duplicated stmgr issue).- Async ack/emit/fail PR is green to > merge. To document the requirements/limitations.- Traffic prediction model > is on going.- There are many old issues/PRs to clean up.* > > On Tue, May 22, 2018 at 1:21 PM, Ning Wang <wangnin...@gmail.com> wrote: > > Hi, > > The heron OSS sync meeting will be happening today at 2.00 pm PDT. > Please use the following hangout link: > https://hangouts.google.com/hangouts/_/streaml.io/oss-heron-sync > ?authuser=0 > > > See you all then. > > > > >
