Hi, Gary Thanks for making quick fix for single release artifact. Let's put a discussion thread first to see what else we need for release before cast another vote.
Also we will attend ApacheCon next week, how about we start and leave discussion thread to next Thursday. Thanks, Yanping -----Original Message----- From: Gary [mailto:ga...@apache.org] Sent: Wednesday, May 04, 2016 9:21 PM To: dev@mnemonic.incubator.apache.org Subject: Re: [VOTE] Apache Incubator Mnemonic Release v0.1.0-incubating Thanks Patrick, I appreciate your advices those are very helpful, we have fixed that according to your guidance. we are going to start next vote soon later, Thanks Henry for closing the previous voting. On 5/4/2016 1:08 PM, Wang, Yanping wrote: > Thanks Patrick. > > Twill release guild is more clear. We will follow the guide and prepare a > single release artifact. > > > Thanks, > Yanping > > > -----Original Message----- > From: Patrick Hunt [mailto:ph...@apache.org] > Sent: Wednesday, May 04, 2016 12:14 PM > To: dev@mnemonic.incubator.apache.org > Subject: Re: [VOTE] Apache Incubator Mnemonic Release v0.1.0-incubating > > -1. You need to have a single "release artifact" that can be signed, > voted on, and published > http://incubator.apache.org/guides/releasemanagement.html > e.g. > http://incubator.apache.org/guides/releasemanagement.html#release-distribution > > In particular the release artifact is typically an archive of your > source repository which exactly matches the source control tag. It's > fine to have other "convenience artifacts", such as binaries and code > jars published to maven, etc..., however those are beyond the scope of > the official "release" itself. > > Unfortunately the incubator release documentation doesn't come out and > say this directly. I looked around but I couldn't find it. Take a look > at something like the Twill release guide, it's a good example of how > most projects (at least the ones I'm familiar with) do it: > http://twill.incubator.apache.org/ReleaseGuide.html > > Do notice the checklist here: > http://incubator.apache.org/guides/releasemanagement.html#check-list > Things such as the disclaimer, notice and license files need to be > contained within the release artifact. > > EOD the release artifact, the source code, is what defines an Apache > "release", and only then once it's been voted upon, etc... More > details here: > http://www.apache.org/dev/release.html#releases > > Note: > > I'd recommend linking to Apache resources, e.g. git.apache.org rather > than github.com in any messaging. > > Let me know if you have any questions (ask on your dev list). The > first release is always the hardest and typically takes some > back/forth. > > Patrick > > On Mon, May 2, 2016 at 10:47 AM, Gary <ga...@apache.org> wrote: >> Hello >> I am pleased to be calling this vote for the source release of Apache >> Mnemonic (incubating) >> mnemonic-0.1.0-incubating. >> >> The source zip, including signatures, digests, etc. can be found at: >> https://repository.apache.org/content/repositories/orgapachemnemonic-1035 >> >> The Git tag is mnemonic-parent-0.1.0-incubating >> The Git commit ID is 5e6e930d5c96568f8369f8123188d009359ba11c >> https://git-wip-us.apache.org/repos/asf?p=incubator-mnemonic.git;a=commit;h=c85ec4941cfba6be0da796c27cd650d92199405d >> >> Release artifacts are signed with the following key: >> https://people.apache.org/keys/committer/garyw.asc >> >> KEYS file available here: >> https://github.com/apache/incubator-mnemonic/blob/master/KEYS >> >> 35 issues were closed/resolved for this release: >> https://issues.apache.org/jira/browse/MNEMONIC >> >> The vote will be open for 72 hours. >> Please download the release candidate and evaluate the necessary items >> including checking hashes, signatures, build from source, and test. The >> please vote: >> >> [ ] +1 Release this package as nifi-0.0.1 >> [ ] +0 no opinion >> [ ] -1 Do not release this package because because... >> >> B.R, >> +Gary. >>
