Hi Julian, I am surprised to read that you feel the project hasn't come up with a plan for an Apache release yet. I feel like we do have a plan. I wonder if your message means that our plan is no good, or just that it isn't clear.
>From my perspective, as a community, we have decided that our next release from master (0.13) is going to be an Apache release. And we're treating it the same way we've treated all our other from-master releases in the past (0.10, 0.11, 0.12, etc). That is to say, we have tagged a set of issues with the release number ( https://github.com/apache/incubator-druid/milestone/25) and we are working to get that list down to zero so we can start doing RCs: either by finishing the tasks or by punting them to future releases. We have some extra Apache stuff in this release, and have an "Apache" label in github that we've been tagging those issues and PRs with. Some relevant changes include the following, 1) https://github.com/apache/incubator-druid/pull/5976 (Update license headers.) 2) https://github.com/apache/incubator-druid/pull/6266 (Rename io.druid to org.apache.druid.) 3) https://github.com/apache/incubator-druid/pull/6215 (Adding licenses and enable apache-rat-plugin.) Based on the tempo so far, I am hoping that we will get this release branched off and start doing RCs later in September. We haven't modified our NOTICE file yet, although I think we'll need to, based on what I've seen on the Incubator site. If you have any advice about what's the minimal set of tasks we should get done before starting to generate and vote on RCs, that would be helpful towards getting it done faster. On Mon, Sep 17, 2018 at 10:45 AM Julian Hyde <jh...@apache.org> wrote: > Druid has been in incubation for several months and has not yet produced > an Apache release. There were initially some issues with IP transfer that > prevented that release, but they are now solved. The release is becoming > urgent, because the code is still not been released under the Apache > license. Can the project please come up with a plan for that release? > > I have seen the following in other incubating projects. They want their > first release to be a “major” release, and then they start asking product > managers to dictate the content and timing of the release, and they ask > their marketing people what they could do to make it a “big splash". Don’t > do that. A release is nothing more than a snapshot of whatever is on the > master branch. Releases must be driven by the community. > > The first Apache release is always more effort than it seems. My advice is > to start as soon as possible, and make its goals as limited as possible. > > Julian (wearing my “mentor” hat) > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > For additional commands, e-mail: dev-h...@druid.apache.org > >
