Re: [Apache Bloodhound] #670: Relation type is empty
#670: Relation type is empty +--- Reporter: olemis | Owner: nobody Type: defect | Status: closed Priority: critical | Milestone: Release 8 Component: relations |Version: Resolution: fixed | Keywords: +--- Changes (by rjollos): * milestone: = Release 8 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/670#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #750: Invalid ticket ID in relation makes ticket view crash
#750: Invalid ticket ID in relation makes ticket view crash +--- Reporter: olemis | Owner: astaric Type: defect | Status: closed Priority: critical | Milestone: Release 8 Component: relations |Version: 0.8.0dev Resolution: fixed | Keywords: +--- Changes (by rjollos): * milestone: = Release 8 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/750#comment:12 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #795: request_factory and environment_factory options point to files in the bloodhound source directory
#795: request_factory and environment_factory options point to files in the bloodhound source directory +--- Reporter: rjollos| Owner: rjollos Type: defect | Status: closed Priority: major | Milestone: Release 8 Component: installer |Version: Resolution: fixed | Keywords: +--- Changes (by rjollos): * status: accepted = closed * resolution: = fixed -- Ticket URL: https://issues.apache.org/bloodhound/ticket/795#comment:11 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #809: Make the installer installable
#809: Make the installer installable --+--- Reporter: gjm | Owner: gjm Type: enhancement | Status: closed Priority: major| Milestone: Release 8 Component: installer|Version: Resolution: fixed| Keywords: --+--- Changes (by rjollos): * status: new = closed * resolution: = fixed -- Ticket URL: https://issues.apache.org/bloodhound/ticket/809#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #613: Add / remove milestone breaks a whole product
#613: Add / remove milestone breaks a whole product ---+--- Reporter: olemis| Owner: gjm Type: defect| Status: closed Priority: blocker | Milestone: Release 8 Component: multiproduct |Version: 0.6.0 Resolution: fixed | Keywords: milestone, postgresql, db, sqlite ---+--- Changes (by rjollos): * status: accepted = closed * resolution: = fixed -- Ticket URL: https://issues.apache.org/bloodhound/ticket/613#comment:24 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] BloodhoundReleaseProcess modified
Page BloodhoundReleaseProcess was changed by rjollos
Diff URL:
https://issues.apache.org/bloodhound/wiki/BloodhoundReleaseProcess?action=diffversion=45
Revision 45
Comment: Use new-style markup on the page.
Changes:
---8--8--8--8--8--8--8--8
Index: BloodhoundReleaseProcess
=
--- BloodhoundReleaseProcess (version: 44)
+++ BloodhoundReleaseProcess (version: 45)
@@ -1,14 +1,13 @@
-= Bloodhound Release Process =
+= Bloodhound Release Process
-=== Prerequisites ===
+=== Prerequisites
1. Commit access to {{{svn.apache.org}}} and {{{dist.apache.org}}}
repositories (in particular the bloodhound parts of these referred to below)
1. PGP code signing key uploaded to a public keyserver and added to your
account details at https://id.apache.org. Details for creating such a key can
be found here: http://www.apache.org/dev/openpgp.html#generate-key
-=== Prepare the release ===
+=== Prepare the release
1. Update files in trunk to reflect the current status:
1. Check out the trunk of bloodhound. For example:
-{{{
-#!sh
+{{{#!sh
svn co https://svn.apache.org/repos/asf/bloodhound/trunk bh_trunk
}}}
1. Review the tickets that have been resolved since the last release, and
update the RELEASE_NOTES file highlighting new features and issues fixed,
optionally including major known issues that remain. The relevant tickets will
usually be associated with a single milestone. However, check for tickets that
are part of this release but have been closed
[query:status=closedresolution=fixedmilestone=component!=siteadmin without
the milestone set]. All of the tickets in the milestone should be resolved when
the release is started. Unresolved tickets that are still part of this
milestone should be unassociated by moving them to another milestone.
@@ -18,8 +17,7 @@
1. Update packages version numbers in {{{bloodhound_package/setup.py}}}
files to reflect the current overall version number (if required). The package
version numbers should have been updated at the start of the release cycle.
1. Commit changes back to trunk.
1. If this is a to be a new x.y release, create a new branch named version
number:
-{{{
-#!sh
+{{{#!sh
svn copy https://svn.apache.org/repos/asf/bloodhound/trunk
https://svn.apache.org/repos/asf/bloodhound/branches/version number -m
branching for new release
}}}
1. Switch the working copy to the new branch.
@@ -27,8 +25,7 @@
svn switch https://svn.apache.org/repos/asf/bloodhound/branches/version
number
}}}
1. On the branch, for each {{{bloodhound_package/setup.cfg}}} file set:
- {{{
- #!ini
+ {{{#!ini
[egg_info]
tag_build =
tag_date = 0
@@ -36,19 +33,16 @@
}}}
Commit changes back to the branch.
1. Export branch to separate directory, named apache-bloodhound-version
number:
-{{{
-#!sh
+{{{#!sh
svn export https://svn.apache.org/repos/asf/bloodhound/branches/version
number apache-bloodhound-version number
}}}
1. Check for open tickets requiring the exclusion of files and directories for
the current release and remove them.
1. Create a tar.gz of that directory:
-{{{
-#!sh
+{{{#!sh
tar -pvczf apache-bloodhound-version number.tar.gz /path/to/directory
}}}
1. Create a detached signature file for the tar.gz file. For example, on the
command line with gpg:
-{{{
-#!sh
+{{{#!sh
gpg --armor --output apache-bloodhound-version number.tar.gz.asc
--detach-sig apache-bloodhound-version number.tar.gz
}}}
1. You may want to verify the signature, particularly if this is the first
time you are signing a release with this key. Look for //Good signature// in
the output:
@@ -56,39 +50,34 @@
$ gpg --verify apache-bloodhound-version number.tar.gz.asc
apache-bloodhound-version number.tar.gz
}}}
1. Create an md5 file for the tar.gz file. For example with gpg:
-{{{
-#!sh
+{{{#!sh
gpg --print-md MD5 apache-bloodhound-version number.tar.gz
apache-bloodhound-version number.tar.gz.md5
}}}
1. Checkout the `bloodhound-dist` directory, remove artifacts from previous
releases and check in the changes.
-{{{
-#!sh
+{{{#!sh
svn co https://dist.apache.org/repos/dist/dev/bloodhound bloodhound_dist_dev
svn rm apache-bloodhound-*
svn ci bloodhound_dist_dev -m removing artifacts from previous release
}}}
1. Copy the {{{.tar.gz}}}, {{{.tar.gz.md5}}} and {{{.tar.gz.asc}}} files
[release files] to the `bloodhound-dist` directory. Add your PGP key to the
`KEYS` file in this directory if it has not been previously added.
-{{{
-#!sh
+{{{#!sh
cp apache-bloodhound-version number.* bloodhound_dist_dev/
svn add bloodhound_dist_dev/apache-bloodhound-version number*
svn commit bloodhound_dist_dev -m adding version number artifacts to the
Bloodhound dist/dev area for release votes
}}}
1. Create a tag for the release
-{{{
-#!sh
+{{{#!sh
svn copy https://svn.apache.org/repos/asf/bloodhound/branches/version number
https://svn.apache.org/repos/asf/bloodhound/tags/version
[Apache Bloodhound] BloodhoundReleaseProcess modified
Page BloodhoundReleaseProcess was changed by rjollos
Diff URL:
https://issues.apache.org/bloodhound/wiki/BloodhoundReleaseProcess?action=diffversion=46
Revision 46
Comment: Path of command was incorrect.
Changes:
---8--8--8--8--8--8--8--8
Index: BloodhoundReleaseProcess
=
--- BloodhoundReleaseProcess (version: 45)
+++ BloodhoundReleaseProcess (version: 46)
@@ -56,7 +56,7 @@
1. Checkout the `bloodhound-dist` directory, remove artifacts from previous
releases and check in the changes.
{{{#!sh
svn co https://dist.apache.org/repos/dist/dev/bloodhound bloodhound_dist_dev
-svn rm apache-bloodhound-*
+svn rm bloodhound_dist_dev/apache-bloodhound-*
svn ci bloodhound_dist_dev -m removing artifacts from previous release
}}}
1. Copy the {{{.tar.gz}}}, {{{.tar.gz.md5}}} and {{{.tar.gz.asc}}} files
[release files] to the `bloodhound-dist` directory. Add your PGP key to the
`KEYS` file in this directory if it has not been previously added.
---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 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 .
[Apache Bloodhound] BloodhoundReleaseProcess modified
Page BloodhoundReleaseProcess was changed by rjollos
Diff URL:
https://issues.apache.org/bloodhound/wiki/BloodhoundReleaseProcess?action=diffversion=47
Revision 47
Comment: Use a shell variable so that commands can be copy-pasted.
Changes:
---8--8--8--8--8--8--8--8
Index: BloodhoundReleaseProcess
=
--- BloodhoundReleaseProcess (version: 46)
+++ BloodhoundReleaseProcess (version: 47)
@@ -16,13 +16,16 @@
1. Update NOTICE and LICENSE files if required (should any licenses be
added/removed; are the locations specified still accurate).
1. Update packages version numbers in {{{bloodhound_package/setup.py}}}
files to reflect the current overall version number (if required). The package
version numbers should have been updated at the start of the release cycle.
1. Commit changes back to trunk.
-1. If this is a to be a new x.y release, create a new branch named version
number:
+1. If this is a to be a new x.y release, create a new branch named version
number. Set a variable in the shell in order to copy and paste the commands
that follow:
{{{#!sh
-svn copy https://svn.apache.org/repos/asf/bloodhound/trunk
https://svn.apache.org/repos/asf/bloodhound/branches/version number -m
branching for new release
+VER=version number
+}}}
+{{{#!sh
+svn copy https://svn.apache.org/repos/asf/bloodhound/trunk
https://svn.apache.org/repos/asf/bloodhound/branches/$VER -m branching for new
release
}}}
1. Switch the working copy to the new branch.
{{{#!sh
-svn switch https://svn.apache.org/repos/asf/bloodhound/branches/version
number
+svn switch https://svn.apache.org/repos/asf/bloodhound/branches/$VER
}}}
1. On the branch, for each {{{bloodhound_package/setup.cfg}}} file set:
{{{#!ini
@@ -32,26 +35,26 @@
tag_svn_revision = false
}}}
Commit changes back to the branch.
-1. Export branch to separate directory, named apache-bloodhound-version
number:
+1. Export branch to separate directory, named apache-bloodhound-$VER:
{{{#!sh
-svn export https://svn.apache.org/repos/asf/bloodhound/branches/version
number apache-bloodhound-version number
+svn export https://svn.apache.org/repos/asf/bloodhound/branches/$VER
apache-bloodhound-$VER
}}}
1. Check for open tickets requiring the exclusion of files and directories for
the current release and remove them.
1. Create a tar.gz of that directory:
{{{#!sh
-tar -pvczf apache-bloodhound-version number.tar.gz /path/to/directory
+tar -pvczf apache-bloodhound-$VER.tar.gz /path/to/directory
}}}
1. Create a detached signature file for the tar.gz file. For example, on the
command line with gpg:
{{{#!sh
-gpg --armor --output apache-bloodhound-version number.tar.gz.asc
--detach-sig apache-bloodhound-version number.tar.gz
+gpg --armor --output apache-bloodhound-$VER.tar.gz.asc --detach-sig
apache-bloodhound-$VER.tar.gz
}}}
1. You may want to verify the signature, particularly if this is the first
time you are signing a release with this key. Look for //Good signature// in
the output:
{{{#!sh
-$ gpg --verify apache-bloodhound-version number.tar.gz.asc
apache-bloodhound-version number.tar.gz
+$ gpg --verify apache-bloodhound-$VER.tar.gz.asc apache-bloodhound-$VER.tar.gz
}}}
1. Create an md5 file for the tar.gz file. For example with gpg:
{{{#!sh
-gpg --print-md MD5 apache-bloodhound-version number.tar.gz
apache-bloodhound-version number.tar.gz.md5
+gpg --print-md MD5 apache-bloodhound-$VER.tar.gz
apache-bloodhound-$VER.tar.gz.md5
}}}
1. Checkout the `bloodhound-dist` directory, remove artifacts from previous
releases and check in the changes.
{{{#!sh
@@ -61,13 +64,13 @@
}}}
1. Copy the {{{.tar.gz}}}, {{{.tar.gz.md5}}} and {{{.tar.gz.asc}}} files
[release files] to the `bloodhound-dist` directory. Add your PGP key to the
`KEYS` file in this directory if it has not been previously added.
{{{#!sh
-cp apache-bloodhound-version number.* bloodhound_dist_dev/
-svn add bloodhound_dist_dev/apache-bloodhound-version number*
-svn commit bloodhound_dist_dev -m adding version number artifacts to the
Bloodhound dist/dev area for release votes
+cp apache-bloodhound-$VER.* bloodhound_dist_dev/
+svn add bloodhound_dist_dev/apache-bloodhound-$VER*
+svn commit bloodhound_dist_dev -m adding $VER artifacts to the Bloodhound
dist/dev area for release votes
}}}
1. Create a tag for the release
{{{#!sh
-svn copy https://svn.apache.org/repos/asf/bloodhound/branches/version number
https://svn.apache.org/repos/asf/bloodhound/tags/version number -m tagging
release
+svn copy https://svn.apache.org/repos/asf/bloodhound/branches/$VER
https://svn.apache.org/repos/asf/bloodhound/tags/$VER -m tagging release
}}}
1. On the trunk, update the packages version numbers in
{{{bloodhound_package/setup.py}}} files to the next development version.
Commit changes back to the trunk.
@@ -81,7 +84,7 @@
svn co https://dist.apache.org/repos/dist/release/bloodhound
