You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <bl...@incubator.apache.org> on 2013/01/08 18:21:09 UTC
[Apache Bloodhound] BloodhoundReleaseProcess added
Page "BloodhoundReleaseProcess" was added by jdreimann
Comment: Initial creation
Content:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
= Bloodhound Release Process =
=== Prerequisites ===
1. Commit access to {{{svn.apache.org/[...]bloodhound}}} and {{{dist.apache.org}}}
1. PGP registered on the Apache ID
=== Prepare the release ===
1. Update the RELEASE_NOTES file highlighting new features and issues fixed
1. Optionally include major known issues that remain
1. Update NOTICES file if required
1. Create branch named <version number>
1. Export branch to separate directory, named apache-bloodhound-incubating-<version number>
1. Zip up that directory in Terminal (OS X 10.8) using: [[br]] {{{tar -pvczf apache-bloodhound-incubating-<version number>.tar.gz /path/to/directory}}}
1. Create .md5 and .asc files for the resulting file
1. Copy the {{{.tar.gz}}}, {{{.tar.gz.md5}}} and {{{.tar.gz.asc}}} files [release files] to the {{{https://dist.apache.org/repos/dist/dev/incubator/bloodhound}}} folder.
=== Voting process ===
1. Call for a vote on the bh-dev@ mailing list
1. Wait at least 72 hours before announcing a result
1. A minimum of three PPMC members need to vote +1 to succeed
1. On replying to announce the results, the subject of the email should be changed to [RESULT] ...
=== Announcing the release ===
1. Copy the release files to the release location: {{{https://dist.apache.org/repos/dist/release/incubator/bloodhound}}}
-------8<------8<------8<------8<------8<------8<------8<------8<--------
--
Page URL: <https://issues.apache.org/bloodhound/wiki/BloodhoundReleaseProcess>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
This is an automated message. Someone added your email address to be
notified of changes on 'BloodhoundReleaseProcess' page.
If it was not you, please report to .
Re: [Apache Bloodhound] BloodhoundReleaseProcess added
Posted by Olemis Lang <ol...@gmail.com>.
On 1/10/13, Joachim Dreimann <jo...@wandisco.com> wrote:
> Agreed.
> No need to be shy Olemis,
/me blushes ... :D
> you can edit the wiki page yourself! :-)
>
I would , but I don't know what you do for release and how you use it
at that time . That's why I wouldn't edit that wiki page . Some kind
of garlic effect ...
o.O
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: [Apache Bloodhound] BloodhoundReleaseProcess added
Posted by Joachim Dreimann <jo...@wandisco.com>.
Agreed.
No need to be shy Olemis, you can edit the wiki page yourself! :-)
On 10 January 2013 03:15, Olemis Lang <ol...@gmail.com> wrote:
> On 1/8/13, Apache Bloodhound <bl...@incubator.apache.org> wrote:
> > Page "BloodhoundReleaseProcess" was added by jdreimann
> > Comment: Initial creation
> > Content:
> > -------8<------8<------8<------8<------8<------8<------8<------8<--------
> >
> > === Prepare the release ===
> > 1. Update the RELEASE_NOTES file highlighting new features and issues
> fixed
> > 1. Optionally include major known issues that remain
> > 1. Update NOTICES file if required
>
> After just a quick reading I wanted to suggest to talk about the role
> of milestones to get those three steps done and also :
>
> - Close milestone before release .
> - Reschedule open tickets for the next one .
> - Consider the summary of closed tickets
> (report or query) to document changes
>
> [...]
>
> --
> Regards,
>
> Olemis.
>
> Blog ES: http://simelo-es.blogspot.com/
> Blog EN: http://simelo-en.blogspot.com/
>
> Featured article:
>
--
Joe Dreimann
UX Designer | WANdisco <http://www.wandisco.com/>
*
*
*Transform your software development department. Register for a free SVN
HealthCheck <http://go.wandisco.com/HealthCheck-Sig.html> *
Re: [Apache Bloodhound] BloodhoundReleaseProcess added
Posted by Olemis Lang <ol...@gmail.com>.
On 1/8/13, Apache Bloodhound <bl...@incubator.apache.org> wrote:
> Page "BloodhoundReleaseProcess" was added by jdreimann
> Comment: Initial creation
> Content:
> -------8<------8<------8<------8<------8<------8<------8<------8<--------
>
> === Prepare the release ===
> 1. Update the RELEASE_NOTES file highlighting new features and issues fixed
> 1. Optionally include major known issues that remain
> 1. Update NOTICES file if required
After just a quick reading I wanted to suggest to talk about the role
of milestones to get those three steps done and also :
- Close milestone before release .
- Reschedule open tickets for the next one .
- Consider the summary of closed tickets
(report or query) to document changes
[...]
--
Regards,
Olemis.
Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/
Featured article:
Re: [Apache Bloodhound] BloodhoundReleaseProcess added
Posted by Joachim Dreimann <jo...@wandisco.com>.
I've added a wiki page with an initial step-by-step guide to releasing a
new Bloodhound version. It's work in progress but probably good enough for
a new release manager to pick up and expand upon. I'll continue adding
information until we call for another release.
That may be soon by the way, once the two remaining blockers are resolved:
https://issues.apache.org/bloodhound/query?priority=blocker&status=!closed
- Joe
On 8 January 2013 17:21, Apache Bloodhound <
bloodhound-dev@incubator.apache.org> wrote:
> Page "BloodhoundReleaseProcess" was added by jdreimann
> Comment: Initial creation
> Content:
> -------8<------8<------8<------8<------8<------8<------8<------8<--------
> = Bloodhound Release Process =
>
> === Prerequisites ===
> 1. Commit access to {{{svn.apache.org/[...]bloodhound}}} and {{{
> dist.apache.org}}}
> 1. PGP registered on the Apache ID
>
> === Prepare the release ===
> 1. Update the RELEASE_NOTES file highlighting new features and issues fixed
> 1. Optionally include major known issues that remain
> 1. Update NOTICES file if required
> 1. Create branch named <version number>
> 1. Export branch to separate directory, named
> apache-bloodhound-incubating-<version number>
> 1. Zip up that directory in Terminal (OS X 10.8) using: [[br]] {{{tar
> -pvczf apache-bloodhound-incubating-<version number>.tar.gz
> /path/to/directory}}}
> 1. Create .md5 and .asc files for the resulting file
> 1. Copy the {{{.tar.gz}}}, {{{.tar.gz.md5}}} and {{{.tar.gz.asc}}} files
> [release files] to the {{{
> https://dist.apache.org/repos/dist/dev/incubator/bloodhound}}} folder.
>
> === Voting process ===
> 1. Call for a vote on the bh-dev@ mailing list
> 1. Wait at least 72 hours before announcing a result
> 1. A minimum of three PPMC members need to vote +1 to succeed
> 1. On replying to announce the results, the subject of the email should be
> changed to [RESULT] ...
>
> === Announcing the release ===
> 1. Copy the release files to the release location: {{{
> https://dist.apache.org/repos/dist/release/incubator/bloodhound}}}
> -------8<------8<------8<------8<------8<------8<------8<------8<--------
>
> --
> Page URL: <
> https://issues.apache.org/bloodhound/wiki/BloodhoundReleaseProcess>
> Apache Bloodhound <https://issues.apache.org/bloodhound/>
> The Apache Bloodhound (incubating) issue tracker
>
> This is an automated message. Someone added your email address to be
> notified of changes on 'BloodhoundReleaseProcess' page.
> If it was not you, please report to .
>
--
Joe Dreimann
UX Designer | WANdisco <http://www.wandisco.com/>
*
*
*Transform your software development department. Register for a free SVN
HealthCheck <http://go.wandisco.com/HealthCheck-Sig.html> *