Don’t include the release candidate suffix (“-rc3”) in the name of the released artifact. Do include ‘-incubating’.
Kylin’s artifacts are good examples to follow: https://dist.apache.org/repos/dist/release/kylin/ By the way, I saw that in git you have tag without the ‘-rc3’, namely ‘release-0.3.0’ tag. This is good. Better would be to have a tag with the same name as the release, namely ‘eagle-0.3.0-incubating’. This is what Kylin does. It’s up to you whether you keep the ‘release-0.3.0-rc3’ tag. I’d be inclined to delete it now the release is out. The hash is already on record in the release vote. Julian > On Apr 8, 2016, at 1:47 PM, Dendukuri, Hemanth <hdenduk...@ebay.com> wrote: > > Julian, Please provide your input. > > > > > On 4/8/16, 12:15 PM, "Zhang, Edward (GDI Hadoop)" <yonzh...@ebay.com> wrote: > >> looks 0.3.0-incubating naming is more informational, like kylin >> https://dist.apache.org/repos/dist/release/kylin/ >> >> On 4/6/16, 2:49, "Dendukuri, Hemanth" <hdenduk...@ebay.com> wrote: >> >>> Hi, >>> >>> I want to upload voted "eagle release candidate 3" artifacts to apache >>> release distribution >>> https://dist.apache.org/repos/dist/release/incubator/eagle/ >>> >>> Should the name of folder/files contain ³rc3² suffix or can I rename it >>> to just "0.3.0-incubating² and have voted rc3 artifacts in it. >>> >>> Regards >>> Hemanth >>
