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 <http://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 <http://incubator.apache.org/guides/releasemanagement.html> [2] http://incubator.apache.org/incubation/Incubation_Policy.html#Releases <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 :)
signature.asc
Description: Message signed with OpenPGP using GPGMail
