GitHub user johnmccabe opened a pull request:
https://github.com/apache/incubator-brooklyn/pull/1170
add getting started vagrant env to release artifacts
- added following inclusion of Vagrant as a target in #1144
- previously at
https://github.com/johnmccabe/vagrant-brooklyn-getting-started
- update release process docs to match current repo structure
- update make-release-artifacts to match current repo structure
- builds/signs/chksums `apache-brooklyn-<VER>-vagrant.tar.gz|zip`
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/johnmccabe/incubator-brooklyn
feature/vagrant-env
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn/pull/1170.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1170
----
commit 9fdca59d230a3459955be4914d569a2dfea0c74b
Author: John McCabe <[email protected]>
Date: 2016-01-21T18:42:08Z
update make-release-artifacts to work with current repo structure
commit 2ee54b0b1c64da44fde987c5a9ebb2883555c87c
Author: John McCabe <[email protected]>
Date: 2016-01-21T18:49:31Z
add apache-brooklyn-VER-vagrant release artifact
commit 1d8b8e920ff9a6b13d0c2f1c373ad4109c27558d
Author: John McCabe <[email protected]>
Date: 2016-01-21T22:03:41Z
update release process docs for current repo structure
commit de945b272cc32f3507d1ae21e98da1e33a4b4f18
Author: John McCabe <[email protected]>
Date: 2016-01-21T22:50:59Z
add getting started vagrant env to release artifacts
- following inclusion of Vagrant as a target in #1144
- previously at
https://github.com/johnmccabe/vagrant-brooklyn-getting-started
commit dc7e8c4a3efbc238cb752b3e453328cdc884da76
Author: John McCabe <[email protected]>
Date: 2016-01-21T22:57:21Z
correct artifact staging dir path
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
