The reply in the ticket is: As you are a podling, please have someone from the IPMC create the dist directories you need.
On Thu, Oct 27, 2016 at 10:32 AM, Edward Capriolo <[email protected]> wrote: > I filed a ticket to cover both: > > https://issues.apache.org/jira/browse/INFRA-12833 > > I think this is the last thing we need. > > Thanks, > Edward > > On Sun, Oct 9, 2016 at 11:50 PM, Josh Elser <[email protected]> wrote: > >> Create a JIRA issue asking INFRA to create the SVN directories: >> >> https://dist.apache.org/repos/dist/release/incubator/gossip >> https://dist.apache.org/repos/dist/dev/incubator/gossip >> >> dist/dev is a good location to stage RCs. Beware that items placed in >> dist/release are automatically mirror'ed out. This should only contain >> artifacts that have been approved via vote. >> >> Check the permissions on your tilde-space. Not sure why this wouldn't >> automatically happen. >> >> Edward Capriolo wrote: >> >>> I have generated a key for signing following the instructions here: >>> http://www.apache.org/dev/release-signing.html >>> >>> I have created a pgp key with the requested strength. >>> http://keys.gnupg.net/pks/lookup?op=get&search=0x843E5702C878C988 >>> >>> I have created a public_html folder on people.apache.org, but I am not >>> seeing the content. http://people.apache.org/~ecapriolo. >>> >>> There are some steps that suggest I should put keys here: >>> >>> https://dist.apache.org/repos/dist/release/incubator-gossip >>> >>> I am not quite sure how to arrange that access. >>> >>> P.Taylor any hints? >>> >>> On Fri, Oct 7, 2016 at 3:47 PM, Edward Capriolo<[email protected]> >>> wrote: >>> >>> I created: >>>> https://issues.apache.org/jira/browse/GOSSIP-27 >>>> >>>> Some of the items I have to handle but others are free to take on /send >>>> PR >>>> for the remaining. >>>> >>>> On Fri, Oct 7, 2016 at 3:43 PM, chandresh pancholi< >>>> [email protected]> wrote: >>>> >>>> Sure Ed. >>>>> Can you create the ticket? >>>>> >>>>> On Sat, Oct 8, 2016 at 1:07 AM, Edward Capriolo<[email protected]> >>>>> wrote: >>>>> >>>>> Good catch. >>>>>> There are a few issues I see. >>>>>> >>>>>> The first is the maven instructions at the bottom, >>>>>> >>>>>> The second is that the build link is wrong. it should be >>>>>> # Apache Gossip  >>>>>> >>>>>> The third is that some of the code examples are slightly dated. >>>>>> >>>>>> Lets open up a ticket to track this and the things p.taylor mentions. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Oct 7, 2016 at 3:25 PM, chandresh pancholi< >>>>>> [email protected]> wrote: >>>>>> >>>>>> We need to change same in project's readme.md. >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Sat, Oct 8, 2016 at 12:40 AM, Edward Capriolo< >>>>>>> >>>>>> [email protected]> >>>>> >>>>>> wrote: >>>>>>> >>>>>>> You might be looking at the wrong project: >>>>>>>> >>>>>>>> https://github.com/edwardcapriolo/incubator-gossip/blob/ >>>>>>>> >>>>>>> master/pom.xml >>>>> >>>>>> >>>>>>>> <parent> >>>>>>>> <groupId>org.apache</groupId> >>>>>>>> <artifactId>apache</artifactId> >>>>>>>> <version>RELEASE</version> >>>>>>>> </parent> >>>>>>>> >>>>>>>> <groupId>org.apache.gossip</groupId> >>>>>>>> <artifactId>gossip</artifactId> >>>>>>>> <name>gossip</name> >>>>>>>> >>>>>>>> A few people seem to be confused because the pre-fork code is also >>>>>>>> >>>>>>> in >>>>> >>>>>> my >>>>>> >>>>>>> github. >>>>>>>> >>>>>>>> On Fri, Oct 7, 2016 at 2:55 PM, P. Taylor Goetz<[email protected]> >>>>>>>> >>>>>>> wrote: >>>>>>> >>>>>>>> I would change the groupId to org.apache.gossip. I’d have to >>>>>>>>> >>>>>>>> check, >>>>> >>>>>> but I >>>>>>> >>>>>>>> think Nexus has rules in place that enforce that, so it’s probably >>>>>>>>> >>>>>>>> best >>>>>> >>>>>>> to >>>>>>>> >>>>>>>>> just go ahead. >>>>>>>>> >>>>>>>>> -Taylor >>>>>>>>> >>>>>>>>> On Oct 7, 2016, at 2:52 PM, chandresh pancholi< >>>>>>>>>> >>>>>>>>> [email protected]> wrote: >>>>>>>>> >>>>>>>>>> +1 for release. >>>>>>>>>> >>>>>>>>>> Concern >>>>>>>>>> Right now groupId on github says io.teknek. Will it change to >>>>>>>>>> org.apache.gossip in first release? >>>>>>>>>> If it changes then we have to remove io.teknek from readme.md >>>>>>>>>> >>>>>>>>>> Thanks >>>>>>>>>> >>>>>>>>>> On Fri, Oct 7, 2016 at 11:55 PM, P. Taylor Goetz< >>>>>>>>>> >>>>>>>>> [email protected]> >>>>>> >>>>>>> wrote: >>>>>>>>> >>>>>>>>>> The typical process is to have a DISCUSS thread before and >>>>>>>>>>> >>>>>>>>>> official >>>>>> >>>>>>> VOTE >>>>>>>> >>>>>>>>> thread, but I assume that was the intent here. >>>>>>>>>>> >>>>>>>>>>> I’m +1 for moving forward with a release. Here are some links >>>>>>>>>>> >>>>>>>>>> to >>>>> >>>>>> some >>>>>>> >>>>>>>> light reading about the process [1][2]. >>>>>>>>>>> >>>>>>>>>>> A quick check of the gossip repo reveals the following that >>>>>>>>>>> >>>>>>>>>> need >>>>> >>>>>> to >>>>>> >>>>>>> be >>>>>>> >>>>>>>> addressed before release: >>>>>>>>>>> >>>>>>>>>>> - DISCLAIMER file needs to be added. >>>>>>>>>>> - NOTICE file needs to added (see [3] for the procedure) >>>>>>>>>>> - KEYS file needs to be created (see [4] for more light >>>>>>>>>>> >>>>>>>>>> reading on >>>>> >>>>>> signing >>>>>>>>> >>>>>>>>>> releases) >>>>>>>>>>> >>>>>>>>>>> The release manager will also need an account on >>>>>>>>>>> >>>>>>>>>> repository.apache.org >>>>>>>> >>>>>>>>> (ASF’s >>>>>>>>> >>>>>>>>>> Nexus instance). >>>>>>>>>>> >>>>>>>>>>> It would also be good, but not required, for the signing key >>>>>>>>>>> >>>>>>>>>> to be >>>>> >>>>>> linked >>>>>>>>> >>>>>>>>>> to the Apache web of trust. >>>>>>>>>>> >>>>>>>>>>> Edward, can I assume you are going to be the release manager >>>>>>>>>>> >>>>>>>>>> for >>>>> >>>>>> the >>>>>> >>>>>>> first >>>>>>>>> >>>>>>>>>> release? If you need any help, feel free to ask. >>>>>>>>>>> >>>>>>>>>>> -Taylor >>>>>>>>>>> >>>>>>>>>>> [1] http://incubator.apache.org/guides/releasemanagement.html >>>>>>>>>>> [2] http://incubator.apache.org/incubation/Incubation_Policy. >>>>>>>>>>> >>>>>>>>>> html#Releases >>>>>>>>> >>>>>>>>>> [3] http://www.apache.org/legal/src-headers.html#notice >>>>>>>>>>> [4] http://www.apache.org/dev/release-signing.html >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Oct 7, 2016, at 3:26 AM, Edward Capriolo< >>>>>>>>>>> >>>>>>>>>> [email protected]> >>>>>> >>>>>>> wrote: >>>>>>>>> >>>>>>>>>> With the additions of: >>>>>>>>>>> https://issues.apache.org/jira/browse/GOSSIP-21 >>>>>>>>>>> https://issues.apache.org/jira/browse/GOSSIP-26 >>>>>>>>>>> >>>>>>>>>>> Apache Gossip has the the ability to create peer to peer >>>>>>>>>>> >>>>>>>>>> systems >>>>> >>>>>> and >>>>>> >>>>>>> share >>>>>>>>> >>>>>>>>>> user defined data between them. Those capabilities prompts me >>>>>>>>>>> >>>>>>>>>> to >>>>> >>>>>> call >>>>>>> >>>>>>>> a >>>>>>>> >>>>>>>>> vote for the first release of Apache Gossip. >>>>>>>>>>> >>>>>>>>>>> The current pom tag is 0.1.0-incubating so I think we should >>>>>>>>>>> >>>>>>>>>> call >>>>> >>>>>> the >>>>>>> >>>>>>>> release version 0.2.0-incubating. >>>>>>>>>>> >>>>>>>>>>> My vote +1 (binding). >>>>>>>>>>> >>>>>>>>>>> Thank you, >>>>>>>>>>> Edward >>>>>>>>>>> >>>>>>>>>>> (Thank you mentors for good nudging :) >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Chandresh Pancholi >>>>>>>>>> Senior Software Engineer >>>>>>>>>> Flipkart.com >>>>>>>>>> Email-id:[email protected] >>>>>>>>>> Contact:08951803660 >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Chandresh Pancholi >>>>>>> Senior Software Engineer >>>>>>> Flipkart.com >>>>>>> Email-id:[email protected] >>>>>>> Contact:08951803660 >>>>>>> >>>>>>> >>>>> >>>>> -- >>>>> Chandresh Pancholi >>>>> Senior Software Engineer >>>>> Flipkart.com >>>>> Email-id:[email protected] >>>>> Contact:08951803660 >>>>> >>>>> >>>> >>> >
