Thanks Julian,
Sure I will update the tag name to "eagle-0.3.0-incubating” and also push
artifacts without suffix (“-rc3”).
On 4/8/16, 3:53 PM, "Julian Hyde" wrote:
>Don’t include the release candidate suffix (“-rc3”) in the name of the
>released artifact. Do include ‘-incubating’.
>
>Ky
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.
Julian, Please provide your input.
On 4/8/16, 12:15 PM, "Zhang, Edward (GDI Hadoop)" 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" wrote:
>
>>Hi,
>>
>>I want to upload vot
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" wrote:
>Hi,
>
>I want to upload voted "eagle release candidate 3" artifacts to apache
>release distribution
>https://dist.apache.org/repos/dist
I just fixed this bug, and we can update the configurations on EAGLE UI
directly.
This configuration refactor only impacts classification pages, which
requires a prefix “web” in front of the properties. For other
configurations, it remains the same.
I will update the doc later.
Best Regards,
Q
I just fixed this bug today, and we can update the configurations on EAGLE
UI directly.
This bug was introduced by a configuration refactor, which only impacts
classification pages, which requires a prefix “web” in front of the
properties.
Later we will update the doc on eagle website.
Best Reg
