Re: Branch name and tag names are confusing

Have to wait for INFRA team's response here. In another thread... On Fri, Apr 22, 2016 at 9:44 AM, Zhao, Qingwen wrote: > Still cannot see the branch Œdev¹ on Github. More than 12 hours have > passed since it¹s created :( > > Regards, > Qingwen Zhao | Apache Eagle > Desk:

Re: Branch name and tag names are confusing

Still cannot see the branch Œdev¹ on Github. More than 12 hours have passed since it¹s created :( Regards, Qingwen Zhao | Apache Eagle Desk: 20998167 | Cell: +86 18818215025 On 4/21/16, 7:11 PM, "Liangfei.Su" wrote: >Seems no objection till now. > >I have created a

Re: Branch name and tag names are confusing

Write a wiki page at: https://cwiki.apache.org/confluence/display/EAG/Branching+Convention as summary of this discussion. Please suggest. We need simple and workable process. On Mon, Apr 11, 2016 at 11:28 AM, Hao Chen wrote: > And also, github support GPG signature

Re: Branch name and tag names are confusing

And also, github support GPG signature verification now: https://github.com/blog/2144-gpg-signature-verification, please make sure making any tag with signature. (Do everything about *Eagle* in security way if possible:-)) - Hao On Mon, Apr 11, 2016 at 11:24 AM, Hao Chen wrote:

Re: Branch name and tag names are confusing

Thanks, Julian. Let's refer to Calcite's practice, define following convention: 1. Tag Name: eagle-${version}, say "eagle-0.3.0-incubating" 2. Branch Name: release-${base-version}, say "release-0.3.0-incubating" Any opinions? - Hao On Mon, Apr 11, 2016 at 4:12 AM, Julian Hyde

Re: Branch name and tag names are confusing

Agree. I think we should make the branch name more clear. (PS: Is these 3 tags in the same commit- 8183eda? If so, I guess should clean some of them) 2016-04-11 4:12 GMT+08:00 Julian Hyde : > It is certainly useful to have a convention. I tend to use the one > supplied by

Re: Branch name and tag names are confusing

It is certainly useful to have a convention. I tend to use the one supplied by maven, which would be “eagle-0.3.0-incubating” (since the project is “eagle” and the version is “0.3.0-incubating”. In Calcite we are now making releases of two different projects (calcite and avatica) from the same

Branch name and tag names are confusing

I found the branch names and tag names are confusing for user. *https://github.com/apache/incubator-eagle/releases * *release-0.3.0-rc3* *eagle-0.3.0-incubating* *release-0.3.0* We should have single tag for each release in format