You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-commits@db.apache.org by ti...@apache.org on 2020/02/17 20:58:21 UTC

[db-jdo] branch tzaeschke-patch-1-HowToRelease created (now 6d486ee)

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

tilmannz pushed a change to branch tzaeschke-patch-1-HowToRelease
in repository https://gitbox.apache.org/repos/asf/db-jdo.git.


      at 6d486ee  Update HowToReleaseJDO.md

This branch includes the following new commits:

     new 6d486ee  Update HowToReleaseJDO.md

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.



[db-jdo] 01/01: Update HowToReleaseJDO.md

Posted by ti...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

tilmannz pushed a commit to branch tzaeschke-patch-1-HowToRelease
in repository https://gitbox.apache.org/repos/asf/db-jdo.git

commit 6d486ee8aae08b07f4a542b6cc22b08ffb6fe834
Author: Tilmann <ti...@apache.org>
AuthorDate: Mon Feb 17 20:58:15 2020 +0000

    Update HowToReleaseJDO.md
---
 HowToReleaseJDO.md | 17 +++++++++++------
 1 file changed, 11 insertions(+), 6 deletions(-)

diff --git a/HowToReleaseJDO.md b/HowToReleaseJDO.md
index 322eed0..74b5430 100644
--- a/HowToReleaseJDO.md
+++ b/HowToReleaseJDO.md
@@ -1,11 +1,20 @@
-= Apache JDO Release Process
+[[index]]
+image:images/JDOx150.png[float="left"]
+image:images/jdo_text.png[float="left"]
+
+'''''
+
+:_basedir: 
+:_imagesdir: images/
+:notoc:
+:titlepage:
+:grid: cols
 
 * xref:procoverview[Overview of the process]
 * xref:procdetail[Detailed process steps]
 * xref:site[Site updates]
 * xref:postrelease[Post release modifications and documentation]
 
-
 == How to Release an Apache JDO Distribution
 
 A distribution of JDO is built from a branch of svn. It is copied into a
@@ -15,7 +24,6 @@ Once released, it is propagated to mirror servers around the world.
 The process is performed by a release manager with cooperation from
 testers in the community.
 
-
 anchor:procoverview[]
 
 === Overview of the process
@@ -65,7 +73,6 @@ If bugs are found or test challenges are sustained after the release is
 approved and distributed, the release manager creates a new branch to
 address the bugs found.
 
-
 anchor:procdetail[]
 
 === Detailed process steps
@@ -194,7 +201,6 @@ community via email to announce@apache.org This must be sent from an
 you will be bombarded with piles of emails from people with "I'm out of
 the Office" as if you really cared ***
 
-
 anchor:site[]
 
 === Site updates
@@ -243,7 +249,6 @@ _docsdir_.
 . Build and test. Follow the instructions in site/HOWTO to push the site
 changes to the Apache web site.
 
-
 anchor:postrelease[]
 
 === Post release modifications and documentation