distributedlog-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leigh Stewart <lstew...@twitter.com.INVALID>
Subject Re: October 2016 Podling Report Draft Feedback
Date Sat, 08 Oct 2016 14:14:39 GMT
Will do.

On Sat, Oct 8, 2016 at 7:11 AM, Sijie Guo <sijie@apache.org> wrote:

> Ah, Chris, thank you so much.
>
> Leigh was helping with the report. Leigh, can you incorporate Chris's
> comments?
>
> - Sijie
>
> On Fri, Oct 7, 2016 at 6:00 PM, Chris Nauroth <cnauroth@hortonworks.com>
> wrote:
>
>> Thank you, Khurrum.
>>
>> I suspect it will be difficult to finalize this roadmap before the report
>> is due.  For now, I suggest just describing current state; list the first
>> Apache release as an item under “most important issues” and mention that
>> the repackaging topic is under discussion under “how has the project
>> developed”.
>>
>> After those changes, I would be ready to enter my mentor sign-off.
>>
>> --Chris Nauroth
>>
>> On 10/7/16, 6:34 AM, "Khurrum Nasim" <khurrumnasimm@gmail.com> wrote:
>>
>>     I am interested in a road map about the first apache release. I think
>> it is
>>     worth having first apache release go out as soon as possible.
>> especially
>>     the repackaging decision.
>>
>>     - KN
>>
>>     On Wed, Oct 5, 2016 at 1:21 PM, Chris Nauroth <cnauroth@apache.org>
>> wrote:
>>
>>     > I have reviewed the current draft of the next podling report.
>>     >
>>     >
>>     >
>>     > http://wiki.apache.org/incubator/October2016
>>     >
>>     >
>>     >
>>     > This looks good, but I’m also wondering if we can give any more
>> specific
>>     > updates about progress toward a first Apache release.  I know there
>> has
>>     > been some discussion of this (e.g. the repackaging decision).  Any
>> progress
>>     > toward a first Apache release would be good to mention.
>>     >
>>     >
>>     >
>>     > Thank you,
>>     >
>>     > --Chris
>>     >
>>     >
>>     >
>>     >
>>
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message