Congrats and Great work Enrico!!
Awesome Job.
On Wed, Nov 22, 2017 at 6:29 PM, Matteo Merli wrote:
> Great work Enrico!
>
> On Wed, Nov 22, 2017 at 12:53 PM Enrico Olivelli
> wrote:
>
> > The Apache BookKeeper team is proud to announce Apache BookKeeper version
> > 4.5.1.
> >
> > Apache BookKe
Great work Enrico!
On Wed, Nov 22, 2017 at 12:53 PM Enrico Olivelli
wrote:
> The Apache BookKeeper team is proud to announce Apache BookKeeper version
> 4.5.1.
>
> Apache BookKeeper is a scalable, fault-tolerant, and low-latency
> storage service optimized for
> real-time workloads. It has been
Thanks for putting all the work into getting this out Enrico.
And congrats on your first release! :)
-Ivan
On Wed, Nov 22, 2017 at 10:31 PM, Sijie Guo wrote:
> Awesome! Well done, Enrico.
>
> Thanks Enrico for doing this release and making this happen. Thanks everyone
> in the community for mak
Awesome! Well done, Enrico.
Thanks Enrico for doing this release and making this happen. Thanks
everyone in the community for making this happen.
- Sijie
On Wed, Nov 22, 2017 at 12:53 PM, Enrico Olivelli
wrote:
> The Apache BookKeeper team is proud to announce Apache BookKeeper version
> 4.5.1
The Apache BookKeeper team is proud to announce Apache BookKeeper version
4.5.1.
Apache BookKeeper is a scalable, fault-tolerant, and low-latency
storage service optimized for
real-time workloads. It has been used for a fundamental service to
build reliable services.
It is also the log segment sto
I put up a PR for this idea: BP-20: github workflow for bookkeeper
proposals.
https://github.com/apache/bookkeeper/pull/760
This is my staging website, to show how the bookkeeper proposals would look
like there.
https://sijie.github.io/bookkeeper-staging-site/community/bookkeeper_proposals/
http
Hi BookKeepers,
I am glad to announce that BookKeeper 4.5.1 is ready.
It is a bugfix release, in particular there are critical fixes about
paraller recovery, rackaware ensamble policy, ledger length for
LedgerHandleAdv and Prometheus stats provider.
We backported a bunch of fixes on tests to improv
Il mer 22 nov 2017, 10:44 Sijie Guo ha scritto:
> On Wed, Nov 22, 2017 at 1:35 AM, Enrico Olivelli
> wrote:
>
> > We could try with the next BP
> > Maybe we'd better do the the migration of existing docs only after seeing
> > that the approach is feasible.
> > My major concern is about non-commi
On Wed, Nov 22, 2017 at 1:35 AM, Ivan Kelly wrote:
> I like it
>
> +1.
>
> The BPs can then be used as a basis for documentation, and they can be
> held open until all documentation for a feature is done.
>
yes, exactly
>
> -Ivan
>
> On Wed, Nov 22, 2017 at 9:30 AM, Sijie Guo wrote:
> > Hi al
On Wed, Nov 22, 2017 at 1:35 AM, Enrico Olivelli
wrote:
> We could try with the next BP
> Maybe we'd better do the the migration of existing docs only after seeing
> that the approach is feasible.
> My major concern is about non-committers
why non-committers is a concern? Non-committers can sti
I like it
+1.
The BPs can then be used as a basis for documentation, and they can be
held open until all documentation for a feature is done.
-Ivan
On Wed, Nov 22, 2017 at 9:30 AM, Sijie Guo wrote:
> Hi all,
>
> I have been thinking of how to improve documentation process for a while.
> We hav
We could try with the next BP
Maybe we'd better do the the migration of existing docs only after seeing
that the approach is feasible.
My major concern is about non-committers.
Anyway who proposes a BP will likely be the lead for the implementation, if
he is not a committer he would be somehow skil
Hi all,
I have been thinking of how to improve documentation process for a while.
We have a good BP process for introducing enhancements, features. However,
this process is not well integrated with our review process, and the
content of a BP is not used for documentation.
I am proposing moving th
13 matches
Mail list logo
