Cool, thanks Sent from my iPhone
> On Apr 20, 2016, at 5:23 PM, Liangfei.Su <suliang...@gmail.com> wrote: > > 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 <h...@apache.org> wrote: >> >> 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 <h...@apache.org> wrote: >>> >>> 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 <jh...@apache.org> wrote: >>>> >>>> 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 git repo, so I’m glad we used >>>> “{project}-{version}” rather than “v{version}”. >>>> >>>> In addition to making a tag for each release, we also post the commit >>>> SHA[1], to make it absolutely clear what source code when into the >> release. >>>> >>>> At some point you might need maintenance branches, e.g. a branch from >>>> which several releases, say 0.3.0-incubating, 0.3.1-incubating, >>>> 0.3.2-incubating are subsequently made. I’m not sure what such branches >>>> should be called. >>>> >>>> Julian >>>> >>>> [1] http://calcite.apache.org/downloads/#source-releases >>>> >>>>> On Apr 10, 2016, at 9:00 AM, Hao Chen <h...@apache.org> wrote: >>>>> >>>>> I found the branch names and tag names are confusing for user. >>>>> >>>>> *https://github.com/apache/incubator-eagle/releases >>>>> <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 "*v${VERSION}*" >>>>> >>>>> And also the branch names: >>>>> >>>>> *branch-0.3.0-rc1* >>>>> *branch-0.3.0* >>>>> >>>>> We should have single branch for each release in format " >>>>> *release-${VERSION}*" >>>>> >>>>> Otherwise the community maybe not know which code is actually released >>>> for >>>>> certain version. >>>>> >>>>> I think it's not very good to create a individual branch or release >> tag >>>> for >>>>> RC. We should make sure the name clear for community and users. >>>>> >>>>> How do you think? >>>>> >>>>> - Hao >>
