[VOTE] Graduate Apache DistributedLog as a subproject of Apache BookKeeper

The Apache DistributedLog community has voted to graduate the project and make it a subproject of Apache BookKeeper. The Apache BookKeeper PMC has also voted to accept DistributedLog as a subproject. The links to the vote threads are the following: DistributedLog PPMC vote: https://mail-search.

Re: [VOTE] Release 0.4.0, release candidate #2

02:52, Sijie Guo wrote: > > Ping? > > If there is no other strong objections here, I'd like to conclude the votes > and proceed the remaining steps for the release. > > - Sijie > > On Fri, Jan 20, 2017 at 10:15 AM, Sijie Guo wrote: > >> >> &g

Re: [VOTE] Release 0.4.0, release candidate #2

> On 19 Jan 2017, at 18:42, Sijie Guo wrote: > > Flavio, > > > > On Wed, Jan 18, 2017 at 10:38 AM, Sijie Guo <mailto:si...@apache.org>> wrote: > > > On Jan 18, 2017 10:37 AM, "Sijie Guo" <mailto:si...@apache.org>> wrote: >

Re: [VOTE] Release 0.4.0, release candidate #2

+1, I have checked the following: - Built both 2.10 and 2.11 from source (skipped tests) - Checksums and signatures - NOTICE and LICENSE - Rat Questions: 1- I'm wondering if the text about Hadoop in NOTICE is necessary. How did you guys end up including it? 2- The tgz bundles do not include any

Re: [VOTE] Release 0.4.0, release candidate #1

release. > > Sijie > > On Jan 12, 2017 3:32 AM, "Flavio Junqueira" <mailto:f...@apache.org>> wrote: > >> Ok, so I've seen the following test cases showing errors: >> >> TestBKDistributedLogManager.testNumberOfTransactionsWithIn >&

Re: [VOTE] Release 0.4.0, release candidate #1

10, Sijie Guo wrote: > > Liang had a pull request for the assembly issue. Going to cancel this vote > and produce a new RC. > > Flavio, what are the tests failed in your case? > > Sijie > > On Jan 10, 2017 9:10 AM, "Flavio Junqueira" <mailto:f...@apache

Re: [VOTE] Release 0.4.0, release candidate #1

Yeah, I can't build because of the same issue: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default) on project distributedlog-service: Failed to create assembly: Error adding file to archive: distributedlog-0.4.0-incubating/distribu

Re: [discuss] Official Slack or Gitter channel for Distributedlog

I'm +1 for Slack. -Flavio > On 14 Dec 2016, at 08:32, Stevo Slavić wrote: > > Either works for me, as long as it's documented in project website and readme > file. > > On Wed, Dec 14, 2016 at 9:16 AM, Xi Liu > wrote: > I would prefer using slack channel. > > - X

Re: [DISCUSSION] First Release

> the current situation with the community. We came to a commitment to merge > Twitter's branch back into bookkeeper 4.5. After that we won't maintain our > own branch and switch to 4.5. > > Hope this make sense. > > Sijie > > On Nov 16, 2016 8:04 PM, "Fla

Re: [DISCUSSION] First Release

It isn't great that DistributedLog is not using the Apache BookKeeper release. Essentially anyone using DistributedLog today needs to use the Twitter branch of BookKeeper, which has diverged from Apache BookKeeper. I'm sure the changes in the Twitter branch are all great, but I'd be more comfort

Re: Distributedlog Podling Report Draft - November 2016

ne. >>> >>> On Tue, Nov 1, 2016 at 1:54 AM, Jia Zhai wrote: >>> >>>> Hi Sijie, >>>> Would you please help address some of Flavio's comments first, You may >>> have >>>> more information for story behind the result. I

Re: Distributedlog Podling Report Draft - November 2016

munity is all involved, then I'd mention it, but as stated it sounds like this is relevant to the BookKeeper community, although it affects this community because of the dependency. > > - Expect to cut a release on Nov. We should mention this above when we refer to the first releas

Re: hundreds of millions of streams?

Perhaps this is an obvious observation, but can't you deploy multiple instances to scale to whatever size you like? -Flavio > On 28 Oct 2016, at 20:27, Poule Dodue wrote: > > I think it would cause more concurrency problems in write operations as > described at page 12 point #2 of this thesis:

Re: Podling Report Reminder - November 2016

Hi Jia, I'd suggest that you put a draft together and share on the list so that we can comment before posting on the wiki. -Flavio > On 27 Oct 2016, at 16:44, Jia Zhai wrote: > > Hi Guys, > If there is an opportunity, I would like to have a try for this month. :) > > Thanks a lot. > -Jia >

Re: [DRAFT] Podling report for September 2016

I have signed off even though it hasn't been updated. Let's leave the improvements to the next report. -Flavio > On 13 Sep 2016, at 02:29, Sijie Guo wrote: > > Gotcha. I will improve the report tonight. > > - Sijie > > On Mon, Sep 12, 2016 at 2:35 AM, Fla

Re: Repackaging the package namespace

It isn't strictly necessary, here is what the documentation says: On Repackaging It is recommended - but not mandated - that source is repackaged under the Apache namespace. There is no need to use the incubator namespace. For example, Java source might be repackaged to org.apache.foo.Bar or a

Re: [DRAFT] Podling report for September 2016

gestion. We should start report these things on next > report. > > - Sijie > > On Fri, Sep 9, 2016 at 2:21 PM, Flavio Junqueira wrote: > >> It looks good. It'd be nice to add some more detail, though. For example: >> >> - Number of jiras created >>

Re: [DRAFT] Podling report for September 2016

It looks good. It'd be nice to add some more detail, though. For example: - Number of jiras created - Number of jiras resolved - Jenkins has been set up - Number of contributors reporting jira issues - Can we quantify a "a few people contributing"? Is that 2-3 or more like 10? - Can we quantify th

Re: [DRAFT] Podling report for September 2016

Will do. -Flavio > On 08 Sep 2016, at 07:59, Sijie Guo wrote: > > I submitted the podling report. > > Can any mentor take a look and sign off? > > - Sijie > > On Wed, Sep 7, 2016 at 10:17 PM, Khurrum Nasim > wrote: > >> It seems that I have troubles with my account. Can anyone submit the >

First release?

No pressure, really, but I was wondering what the plan for the first release is. Better to do a first release sooner than later. You already have a working system so it is mostly about sorting out any issues related to releasing in Apache. -Flavio

Re: [draft] Podling report for August 2016

> of? >>>>> There is currently no issue. >>>>> >>>>> How has the community developed since the last report? >>>>> * A few people have started to report issues >>>>> * Some conversations have been initiated on the mailing >&g

Re: [draft] Podling report for August 2016

Thanks for putting this together, Franck. A few things that might be worth adding: - Status page is up and we have started filling it out - Most accounts of initial committers have been created - Jira queue has been created - Repository has been created -Flavio > On 28 Jul 2016, at 19:19, Chris

Committers

Have all committers submitted an ICLA and subscribed to this list? -Flavio

DL Jira

Jira is set up and I have added Sijie, Henry, and Chris as administrators. -Flavio

Re: Board Report?

d that you guys wait. Reports were due last > Wednesday, we usually give a little bit of buffer. At this point, all sign > offs should have happened so you'll be really late. Its no big deal, don't > look at it as a bad mark. > > I'll move the podling over this evening

Re: Board Report?

Hi John, It looks like folks want to submit the report this month, Sijie copied here is working on one and will update it. -Flavio > On 10 Jul 2016, at 16:46, Flavio Junqueira wrote: > > Twitter is still working on the SGA, so moving to group 2 sounds like a good > option.

Re: [DRAFT] DistributedLog Report

> We setup the mail lists, and are moving the repo from GitHub to apache > but waiting for Twitter's SGA. Date of last release: > N/AWhen were the last committers or PMC members elected? > N/ASigned-off-by: [ ](distributedlog) Flavio Junqueira [ > ](distributedlog) Chris Nauroth [ ](distributedlog) Henry > SaputraShepherd/Mentor notes: > > - Sijie

Re: Incubator report for July

I hadn't seen this message before I responded to John about moving to group 2. I'm fine either way, we can report that we have the mailing lists created and we are waiting on the SGA. I don't think we can say anything else, but if you feel that's enough, Henry, let's respond to John to say that

Re: Board Report?

Twitter is still working on the SGA, so moving to group 2 sounds like a good option. -Flavio > On 09 Jul 2016, at 16:23, John D. Ament wrote: > > DistributedLog, > > Do you plan to submit a board report this month? If not, I will move you > to reporting group 2 and monthly August -> October