This is an automated email from the ASF dual-hosted git repository.

zregvart pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-website.git


The following commit(s) were added to refs/heads/master by this push:
     new bfd46b5  fix: paragraphs on blog post
bfd46b5 is described below

commit bfd46b5a1a5a526c6af2065ed86c0da7812a4822
Author: Zoran Regvart <zregv...@apache.org>
AuthorDate: Wed Oct 2 14:45:13 2019 +0200

    fix: paragraphs on blog post
---
 content/blog/Camel3-2monthsaway/index.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/content/blog/Camel3-2monthsaway/index.md 
b/content/blog/Camel3-2monthsaway/index.md
index 34a3e31..5ae1bff 100644
--- a/content/blog/Camel3-2monthsaway/index.md
+++ b/content/blog/Camel3-2monthsaway/index.md
@@ -7,8 +7,11 @@ preview: Status update on Camel 3 only 2 months away
 ---
 
 The Camel team is busy working on the last set of work for Apache Camel 3. 
Today the 2nd release candidate was built and published on a staging repository 
for [early adapters to give it a 
try](https://mail-archives.apache.org/mod_mbox/camel-dev/201910.mbox/%3CCADL1oAqjZVvbJ1cnxqzdcUk%2BkuyCMdyc7w8agZuoN6SYZjPDnA%40mail.gmail.com%3E).
+
 As I am busy myself then I just wanted to write a short blog post to keep the 
community posted that Apache Camel 3 is on the way, and that we expect it to be 
released by end of this year (sometime in November or December).
+
 The latest deadline is to release Camel 3.0 before December 19th 2019 as it 
was exactly on that day 1 year ago, we switched the master branch to become the 
work branch for Apache Camel 3. That means the total development time for Camel 
3 would be 1 year.
+
 Here is a illustration that highlights the timeline of Camel 3:
 
 {{< image "camel3-progress.png" "Camel 3 timeline" >}}

Reply via email to