Re: Considering 0.12.2 release
Why won't release 13.0 instead (as non-Apache)? On Thu, 21 Jun 2018, 08:18 Gian Merlino, wrote: > +1 > > I would suggest adding these two as well. > > https://github.com/druid-io/druid/pull/5878 - Fix inefficient available > segment cache population in SQLMetadataSegmentManager. > https://github.com/druid-io/druid/pull/5873 - HdfsDataSegmentPusher: Close > tmpIndexFile before copying it. > > On Tue, Jun 12, 2018 at 11:34 AM Prashant Deva > wrote: > > > +1 > > > > On Fri, Jun 8, 2018 at 3:37 PM Jihoon Son wrote: > > > > > Hi guys, > > > > > > we have a couple of bug fix PRs available and some of them fix > regression > > > bugs. > > > > > > Here is the list of currently available bug fix PRs which are not > > included > > > in 0.12.1. > > > > > > Regression bug fixes > > > - https://github.com/druid-io/druid/pull/5858 > > > - https://github.com/druid-io/druid/pull/5805 > > > - https://github.com/druid-io/druid/pull/5807 > > > > > > Non-regression bug fixes > > > - https://github.com/druid-io/druid/pull/5850 > > > - https://github.com/druid-io/druid/pull/5815 > > > - https://github.com/druid-io/druid/pull/5856 > > > > > > I think it's worth to make another release for users. > > > > > > Welcome any idea. > > > > > > Jihoon > > > > > -- > > Prashant > > >
Re: Considering 0.12.2 release
+1 I would suggest adding these two as well. https://github.com/druid-io/druid/pull/5878 - Fix inefficient available segment cache population in SQLMetadataSegmentManager. https://github.com/druid-io/druid/pull/5873 - HdfsDataSegmentPusher: Close tmpIndexFile before copying it. On Tue, Jun 12, 2018 at 11:34 AM Prashant Deva wrote: > +1 > > On Fri, Jun 8, 2018 at 3:37 PM Jihoon Son wrote: > > > Hi guys, > > > > we have a couple of bug fix PRs available and some of them fix regression > > bugs. > > > > Here is the list of currently available bug fix PRs which are not > included > > in 0.12.1. > > > > Regression bug fixes > > - https://github.com/druid-io/druid/pull/5858 > > - https://github.com/druid-io/druid/pull/5805 > > - https://github.com/druid-io/druid/pull/5807 > > > > Non-regression bug fixes > > - https://github.com/druid-io/druid/pull/5850 > > - https://github.com/druid-io/druid/pull/5815 > > - https://github.com/druid-io/druid/pull/5856 > > > > I think it's worth to make another release for users. > > > > Welcome any idea. > > > > Jihoon > > > -- > Prashant >
Re: Druid repo migration plan
+1; thanks Jon! On Wed, Jun 20, 2018 at 5:52 PM Jihoon Son wrote: > +1 > > Sounds good to me. > > Jihoon > > On Wed, Jun 20, 2018 at 5:12 PM Nishant Bangarwa < > nbanga...@hortonworks.com> > wrote: > > > +1 > > > > -- > > Nishant Bangarwa > > > > Hortonworks > > > > On 6/20/18, 3:57 PM, "Jonathan Wei" wrote: > > > > Hi all, > > > > The SGA for Druid has been sorted out, we can get started on > migrating > > the > > old Github repo to Apache. > > > > Based on the discussion in our previous migration thread ( > > > > > https://groups.google.com/forum/#!msg/druid-development/q1ip-L8xpBk/GPK1LhC7BQAJ > > ), > > it seems we favor using our existing Github PR and issues workflows. > > > > I'll file a JIRA ticket requesting transfer of > > https://github.com/druid-io/druid to a Gitbox-style Apache repo, > > keeping > > the existing history of PRs/issues/stars/etc. (e.g., Superset: > > https://github.com/apache/incubator-superset) > > > > Before I do that, I wanted to open this thread for a vote to confirm > > that > > we're all okay with this plan, so please chime in with an approval or > > any > > concerns that you may have. > > > > Thanks, > > Jon > > > > > > >
Re: Druid repo migration plan
+1 Sounds good to me. Jihoon On Wed, Jun 20, 2018 at 5:12 PM Nishant Bangarwa wrote: > +1 > > -- > Nishant Bangarwa > > Hortonworks > > On 6/20/18, 3:57 PM, "Jonathan Wei" wrote: > > Hi all, > > The SGA for Druid has been sorted out, we can get started on migrating > the > old Github repo to Apache. > > Based on the discussion in our previous migration thread ( > > https://groups.google.com/forum/#!msg/druid-development/q1ip-L8xpBk/GPK1LhC7BQAJ > ), > it seems we favor using our existing Github PR and issues workflows. > > I'll file a JIRA ticket requesting transfer of > https://github.com/druid-io/druid to a Gitbox-style Apache repo, > keeping > the existing history of PRs/issues/stars/etc. (e.g., Superset: > https://github.com/apache/incubator-superset) > > Before I do that, I wanted to open this thread for a vote to confirm > that > we're all okay with this plan, so please chime in with an approval or > any > concerns that you may have. > > Thanks, > Jon > > >
Re: Druid repo migration plan
+1 -- Nishant Bangarwa Hortonworks On 6/20/18, 3:57 PM, "Jonathan Wei" wrote: Hi all, The SGA for Druid has been sorted out, we can get started on migrating the old Github repo to Apache. Based on the discussion in our previous migration thread ( https://groups.google.com/forum/#!msg/druid-development/q1ip-L8xpBk/GPK1LhC7BQAJ), it seems we favor using our existing Github PR and issues workflows. I'll file a JIRA ticket requesting transfer of https://github.com/druid-io/druid to a Gitbox-style Apache repo, keeping the existing history of PRs/issues/stars/etc. (e.g., Superset: https://github.com/apache/incubator-superset) Before I do that, I wanted to open this thread for a vote to confirm that we're all okay with this plan, so please chime in with an approval or any concerns that you may have. Thanks, Jon
Druid repo migration plan
Hi all, The SGA for Druid has been sorted out, we can get started on migrating the old Github repo to Apache. Based on the discussion in our previous migration thread ( https://groups.google.com/forum/#!msg/druid-development/q1ip-L8xpBk/GPK1LhC7BQAJ), it seems we favor using our existing Github PR and issues workflows. I'll file a JIRA ticket requesting transfer of https://github.com/druid-io/druid to a Gitbox-style Apache repo, keeping the existing history of PRs/issues/stars/etc. (e.g., Superset: https://github.com/apache/incubator-superset) Before I do that, I wanted to open this thread for a vote to confirm that we're all okay with this plan, so please chime in with an approval or any concerns that you may have. Thanks, Jon
Re: Podling Report Reminder - June 2018
The pulsar community is aware that for convenience, they can continue to make releases using their pre-Apache process. As well as the caveat that any such releases are not hosted on ASF infrastructure, and are flagged with a prominent notice that such releases are not Apache releases. Many projects do this early in incubation to maintain their release rhythm. As a mentor I think all is good in that respect. I look forward to an Apache release, and it seems one is likely soon. -Taylor > On Jun 20, 2018, at 5:43 PM, Gian Merlino wrote: > > Hi Justin, > > As Julian said, he is active, and has been very helpful as a mentor. > (Thanks Julian!!) > > Thanks for checking up on us. We'll make sure not to miss next month's > report; we are aware they are a thing (we did a couple already -- Nishant > did one and I did one or two) but it looks like nobody noticed this one > until it was too late. About the non-ASF releases: I don't have a link > handy to the thread, but basically what is going on is that until recently > we didn't have the SGA sorted, which we understood to mean it was out of > the question to do ASF releases. Now it is sorted and we're looking to > migrate our git repos next. I think it is likely we'll want to do another > non-incubator minor release while that process is ongoing, but am still > optimistic that the next major release will be an incubator release. > > On Tue, Jun 19, 2018 at 6:00 PM Justin Mclean > wrote: > >> Hi, >> >> I noticed the podling has failed to report this month and so will need two >> report next month. You're a relatively new podling so I wonder are you just >> not aware of the process or is it that you need more help from your >> mentors? Are your mentors currently active? >> >> I also notice on your dev list a number of votes for non ASF releases. I >> can’t see (but may of missed it) any discussion to why these non ASF >> releases are needed or what is holding you up making an ASF release. It >> seems a little odd to me that you would vote on these and then not get the >> IPMC to look at them, so it may be good idea to have the IPMC look at these >> releases in the future, but hopefully your next release will be an ASF one >> and will be voted on by the IPMC. >> >> Thanks, >> Justin >> - >> To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org >> For additional commands, e-mail: dev-h...@druid.apache.org >> >> - To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org For additional commands, e-mail: dev-h...@druid.apache.org
Re: Podling Report Reminder - June 2018
Hi Justin, As Julian said, he is active, and has been very helpful as a mentor. (Thanks Julian!!) Thanks for checking up on us. We'll make sure not to miss next month's report; we are aware they are a thing (we did a couple already -- Nishant did one and I did one or two) but it looks like nobody noticed this one until it was too late. About the non-ASF releases: I don't have a link handy to the thread, but basically what is going on is that until recently we didn't have the SGA sorted, which we understood to mean it was out of the question to do ASF releases. Now it is sorted and we're looking to migrate our git repos next. I think it is likely we'll want to do another non-incubator minor release while that process is ongoing, but am still optimistic that the next major release will be an incubator release. On Tue, Jun 19, 2018 at 6:00 PM Justin Mclean wrote: > Hi, > > I noticed the podling has failed to report this month and so will need two > report next month. You're a relatively new podling so I wonder are you just > not aware of the process or is it that you need more help from your > mentors? Are your mentors currently active? > > I also notice on your dev list a number of votes for non ASF releases. I > can’t see (but may of missed it) any discussion to why these non ASF > releases are needed or what is holding you up making an ASF release. It > seems a little odd to me that you would vote on these and then not get the > IPMC to look at them, so it may be good idea to have the IPMC look at these > releases in the future, but hopefully your next release will be an ASF one > and will be voted on by the IPMC. > > Thanks, > Justin > - > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > For additional commands, e-mail: dev-h...@druid.apache.org > >
