[GitHub] sijie closed pull request #1714: Fix release notes for 4.8.0

[GitBox <gi...@apache.org>]

sijie closed pull request #1714: Fix release notes for 4.8.0
URL: https://github.com/apache/bookkeeper/pull/1714
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/site/docs/4.8.0/overview/releaseNotes.md b/site/docs/4.8.0/overview/releaseNotes.md
index 7614131d64..02012cfe80 100644
--- a/site/docs/4.8.0/overview/releaseNotes.md
+++ b/site/docs/4.8.0/overview/releaseNotes.md
@@ -13,20 +13,15 @@ this release are summarized below.
 
 ## Highlights
 
-The main features in 4.8.0 cover are around following areas:
+The main features in 4.8.0 are around following areas:
 
-- Public API
 - Durability
 - ExplicitLAC feature
 - New Table Storage Service
 - Bug Fixes
 
 
-### Public API
-
-There are multiple new client features introduced in 4.8.0. Here are two highlighted features:
-
-#### New WriteFlag DEFERRED_SYNC
+### New WriteFlag DEFERRED_SYNC
 
 The writer may ask for temporary relaxed durability writes, that is to receive early acknowledge from Bookies, before an fsync() on Journal.
 Together with this new flag we introduced the new WriteHandle#force() API, this this API the writer is able to request an explicit guarantee of durability to the Bookies
@@ -34,33 +29,33 @@ it is mostly like and explicit fsync() on a file system.
 
 See [`DEFERRED_SYNC`](../javadoc/org/apache/bookkeeper/client/api/WriteFlag) and [force()](../javadoc/org/apache/bookkeeper/client/api/ForceableHandle) for reference
 
-#### New behaviour for Netty ByteBuf reference count management
+### New behaviour for Netty ByteBuf reference count management
 
 All the client side APIs which take ByteBufs now will have the net effect of decrementing by 1 the refcount.
 This is consistent with general contract of Netty.
 It is expected that the client passes the ownership of the ByteBuf to BookKeeper client.
 
-#### Multiple Active Entrylogs
+### Multiple Active Entrylogs
 
 It is now possible on the Bookie to have multiple active entry loggers,
 this new feature will help with compaction performance and some specific workloads.
 
 See [Multiple active entrylogs](https://github.com/apache/bookkeeper/issues/570)
 
-## Table Storage Service
+### Table Storage Service
 
 From this version we are providing the a table (key/value) service embedded in Bookies.
  
 See [BP-30: BookKeeper Table Service](https://github.com/apache/bookkeeper/issues/1205)
 
-## Make ExplicitLAC persistent
+### Make ExplicitLAC persistent
 
 ExplicitLAC was contributed from Salesforce in 4.5.0 release, but in the first release
 it was a beft-effort in-memory mechanism. Now you can configure Bookies to store durably ExplicitLAC.
 
 See [Make ExplicitLAC persistent](https://github.com/apache/bookkeeper/issues/1527)
 
-## Ensemble change on Delayed Write Failure
+### Ensemble change on Delayed Write Failure
 
 We are handling more gracefully the case of a failure of a Bookie in spite of a succeeded write.
 If you are writing with Ack Quorum = 2 and Write Quorum = 3, writes will succeeed even if 1 of 3 Bookies fail,
diff --git a/site/releases.md b/site/releases.md
index 38ffc86765..d7888fb8fc 100644
--- a/site/releases.md
+++ b/site/releases.md
@@ -66,7 +66,10 @@ Client Guide | API docs
 
 ### 26 September, 2018 Release 4.8.0 available
 
-[INSERT SUMMARY]
+This is the 13th release of Apache BookKeeper !
+
+The 4.8.0 release incorporates hundreds of bug fixes, improvements, and features since previous major release, 4.7.0.
+It is a new big milestone in Apache BookKeeper community, this release include great new features, like Relaxed Durability, Stream Storage service and Multiple Active Entrylogs.
 
 ### 29 August, 2018: Release 4.7.2 available
 


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services