+1. [Test Results](#test)
+
+## a id=intro/aIntroduction
+
+You can read the official announcement at [Apache jclouds 1.8.0
released](TODO). You can read the details of the specific JIRA issues
addressed in this release at the [JIRA Release
+
+## a id=intro/aIntroduction
+
+You can read the official announcement at [Apache jclouds 1.8.0
released](TODO). You can read the details of the specific JIRA issues
addressed in this release at the [JIRA Release
Sorry I was traveling this weekend; I can work on the release notes more
tomorrow.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/114#issuecomment-51022978
\ No newline at end of file
+latest_version: 1.8.0
+latest_version_date: 2014-08-TODO
+latest_snapshot: 2.0.0-SNAPSHOT
Onwards to 2.0.0! Can you push these new versions to master which still have
1.8.0-SNAPSHOT?
---
Reply to this email directly or view it on GitHub:
\ No newline at end of file
+latest_version: 1.8.0
+latest_version_date: 2014-08-TODO
+latest_snapshot: 2.0.0-SNAPSHOT
Can you push these new versions to master which still have 1.8.0-SNAPSHOT?
See the vote discussion thread - I was planning to push a commit to update
master to
any thoughts?
Thanks for the explanation. I'm also fine with adding a section to the AWS
guide. The main reason I was suggesting a Getting Started Guide rather than a
README is that most of the READMEs for APIs and providers are very stubby
and/or not very useful, and the result is that users
Squashed down to one commit.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/56#issuecomment-51030090
+
+## a id=intro/aIntroduction
+
+You can read the official announcement at [Apache jclouds 1.8.0
released](TODO). You can read the details of the specific JIRA issues
addressed in this release at the [JIRA Release
+author: a href=...Andrew Phillips/a
+comments: true
+date: 2014-08-02 14:00:00+00:00
+layout: post
+slug: 1-release-2-committers
+title: 1 release, 2 committers...a busy week for jclouds!
+image: /img/posts/TODO.jpg
+---
+
+img class=img-right src=/img/posts/TODO.jpg/There's a lot going
+* TODO: something about SoftLayer?
+* TODO: what's new in OpenStack?
+* TODO: what's new in Rackspace?
+* TODO: announce the version of Guava (16, right)?
+* TODO: other providers
+* This is the last version of jclouds to support Java 6. The next major
version will be based on Java 7. If
[
https://issues.apache.org/jira/browse/JCLOUDS-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Phillips updated JCLOUDS-496:
Fix Version/s: (was: 1.8.0)
2.0.0
TemplateOptions
+* TODO: something about SoftLayer?
+* TODO: what's new in OpenStack?
+* TODO: what's new in Rackspace?
+* TODO: announce the version of Guava (16, right)?
+* TODO: other providers
+* This is the last version of jclouds to support Java 6. The next major
version will be based on Java 7. If
+author: a href=...Andrew Phillips/a
+comments: true
+date: 2014-08-02 14:00:00+00:00
+layout: post
+slug: 1-release-2-committers
+title: 1 release, 2 committers...a busy week for jclouds!
+image: /img/posts/TODO.jpg
+---
+
+img class=img-right src=/img/posts/TODO.jpg/There's a lot going
Committed to
[master](https://git-wip-us.apache.org/repos/asf?p=jclouds-examples.git;a=commit;h=276f6caa0e975ee0af8ca206de1da5524d0e92a8).
Thanks, @najtmar!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-examples/pull/56#issuecomment-51035780
@@ -318,6 +318,21 @@ public Blob getBlob(String container, String key,
GetOptions getOptions) {
}
/**
+* Retrieves the blob
[minor] Retrieves a blob using default options?
---
Reply to this email directly or view it on GitHub:
@@ -318,6 +318,21 @@ public Blob getBlob(String container, String key,
GetOptions getOptions) {
}
/**
+* Retrieves the blob
+* This operation will take several hours.
+*
+* @param container
+* container name
+* @param key
+* blob
The main reason I was suggesting a Getting Started Guide rather than a README
is that most of the READMEs for APIs and providers are very stubby and/or not
very useful, and the result is that users are simply unlikely to look there.
I agree with this, maybe this is something we need to
[jclouds » jclouds-labs-aws
#1242](https://buildhive.cloudbees.com/job/jclouds/job/jclouds-labs-aws/1242/)
SUCCESS
This pull request looks good
[(what's this?)](https://www.cloudbees.com/what-is-buildhive)
---
Reply to this email directly or view it on GitHub:
[jclouds-labs-aws-pull-requests
#116](https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws-pull-requests/116/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-aws/pull/55#issuecomment-51038165
Thanks, @rcoedo! Just a couple of questions regarding the Javadoc.
Is this addition tested anywhere..?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-aws/pull/55#issuecomment-51038844
Unfortunately we don't have any tests for the glacier blobstore yet. I tried to
adapt the base blobstore tests to the glacier implementation but it just
doesn't fit, it would take days to run those. Obviously this is something that
needs to be worked out, for now, I've tested the class manually
+date: 2014-08-02 14:00:00+00:00
+layout: post
+slug: 1-release-2-committers
+title: 1 release, 2 committers...a busy week for jclouds!
+image: /img/posts/chris-and-andrea.jpg
+---
+
+img class=img-right src=/img/posts/chris-and-andrea.png/There's a lot
going on this week for the jclouds
+1
Once comments are addressed.
Thanks @demobox!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/116#issuecomment-51082662
I'm all for enabling the build failure. I don't think someone looking at the
Checkstyle warnings and saying fix x, y, and z warning is a good use of review
time. Checkstyle should simply fail the build. Then we know both locally and in
the build that the code is clean w.r.t Checkstyle.
For
+1 after comments addressed.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/462#issuecomment-51085775
[
https://issues.apache.org/jira/browse/JCLOUDS-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14084897#comment-14084897
]
Diwaker Gupta commented on JCLOUDS-645:
---
[~ccustine] wrote:
My question is whether
[
https://issues.apache.org/jira/browse/JCLOUDS-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14084949#comment-14084949
]
Luciano Sabença commented on JCLOUDS-624:
-
A little late, but just to thank you!
I don't understand this change, why do we use Checkstyle on XML and JSON files?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/464#issuecomment-51094552
You can merge this Pull Request by running:
git pull https://github.com/rcoedo/jclouds-examples master
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-examples/pull/58
-- Commit Summary --
* Add glacier example
-- File Changes --
A
+* TODO: something about SoftLayer?
+* TODO: what's new in OpenStack?
+* TODO: what's new in Rackspace?
+* TODO: announce the version of Guava (16, right)?
+* TODO: other providers
+* This is the last version of jclouds to support Java 6. The next major
version will be based on Java 7. If
[jclouds-site-pull-requests
#367](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/367/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/116#issuecomment-51115530
Go to
http://3db9c8c1f1174b1f3ae1-ca8732c7c93beba21b0a894903015383.r83.cf5.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/116#issuecomment-51115769
Closed #116.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/116#event-148973774
Committed to
[master](https://git-wip-us.apache.org/repos/asf?p=jclouds-site.git;a=commit;h=3a26b3f0fc2e5082992bcb0ded830636e5a886f5)
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/116#issuecomment-51118047
+1
rackspace-cloudidentity is definitely the proper home for this (legacy) code.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds/pull/461#issuecomment-51119001
@everett-toews: Does this merit a jclouds adds two new committers: Andrea
Turli and Chris Custine quicknew?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/commit/3a26b3f0fc2e5082992bcb0ded830636e5a886f5#commitcomment-7260833
+1 to the quick new.
Also a quick new and a page for the ApacheCon EU would be great. I'm AFK until
August 18, but will happily add both if no one has done it before.
---
Reply to this email directly or view it on GitHub:
You can merge this Pull Request by running:
git pull https://github.com/jclouds/jclouds-site committer-quicknew
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/117
-- Commit Summary --
* Adding quicknew for new committers
-- File
+1 - looks good to me. Please squash'n'rebase, and we should be good to go.
Thanks, @rcoedo!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-aws/pull/55#issuecomment-51128638
[jclouds-site-pull-requests
#368](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/368/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/117#issuecomment-51128822
There we go, thanks @demobox!
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-aws/pull/55#issuecomment-51128923
Go to
http://3f001400f5f295dcdbc7-7fed702452ecb2c71be01df58cf1d515.r97.cf5.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/117#issuecomment-51128986
OK...that didn't seem to work:
Any ideas what might be going wrong here?
/cc @nacx @everett-toews
---
Reply to this email directly or view it on GitHub:
Any ideas what might be going wrong here?
Ah...I suspect this may only be supported in items under `news/`?
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/117#issuecomment-51129214
[jclouds-labs-aws-pull-requests
#117](https://jclouds.ci.cloudbees.com/job/jclouds-labs-aws-pull-requests/117/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-labs-aws/pull/55#issuecomment-51129515
Shri Javadekar created JCLOUDS-648:
--
Summary: putBlob operation does not throw a
ContainerNotFoundException against Swift based blobstores
Key: JCLOUDS-648
URL: https://issues.apache.org/jira/browse/JCLOUDS-648
Sunil Shah created JCLOUDS-649:
--
Summary: Creating an image from a root persistent disk causes
NullPointerException on GCE
Key: JCLOUDS-649
URL: https://issues.apache.org/jira/browse/JCLOUDS-649
Shri Javadekar created JCLOUDS-650:
--
Summary: getBlob for non-existent containers does not throw a
ContainerNotFoundException
Key: JCLOUDS-650
URL: https://issues.apache.org/jira/browse/JCLOUDS-650
[
https://issues.apache.org/jira/browse/JCLOUDS-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sunil Shah updated JCLOUDS-649:
---
Description:
When we create an image using the instructions at
[
https://issues.apache.org/jira/browse/JCLOUDS-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sunil Shah updated JCLOUDS-649:
---
Description:
When we create an image using the instructions at
[
https://issues.apache.org/jira/browse/JCLOUDS-648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14085592#comment-14085592
]
Shri Javadekar commented on JCLOUDS-648:
This is so weird. Sometimes I get a
\ No newline at end of file
+latest_version: 1.8.0
+latest_version_date: 2014-08-TODO
+latest_snapshot: 2.0.0-SNAPSHOT
Prefer to change to 2.0.0 as soon as possible.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/114/files#r15795248
+**Note: 1.8.0 will be the last major version of jclouds to support Java 6**
+
+## a id=highlights/aHighlights
+
+* TODO: something about SoftLayer?
+* TODO: what's new in OpenStack?
+* TODO: what's new in Rackspace?
+* TODO: announce the version of Guava (16, right)?
+* TODO: other
+* TODO: something about SoftLayer?
+* TODO: what's new in OpenStack?
+* TODO: what's new in Rackspace?
+* TODO: announce the version of Guava (16, right)?
+* TODO: other providers
+* This is the last version of jclouds to support Java 6. The next major
version will be based on Java 7. If
+
+## a id=intro/aIntroduction
+
+You can read the official announcement at [Apache jclouds 1.8.0
released](TODO). You can read the details of the specific JIRA issues
addressed in this release at the [JIRA Release
+1. [Known Issues](#issues)
+1. [Reminder](#reminder)
+1. [Credits](#credits)
+1. [Test Results](#test)
+
+## a id=intro/aIntroduction
+
+You can read the official announcement at [Apache jclouds 1.8.0
released](TODO). You can read the details of the specific JIRA issues
addressed in
+1. [Test Results](#test)
+
+## a id=intro/aIntroduction
+
+You can read the official announcement at [Apache jclouds 1.8.0
released](TODO). You can read the details of the specific JIRA issues
addressed in this release at the [JIRA Release
Made some substantial additions.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/114#issuecomment-51150670
[jclouds-site-pull-requests
#369](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/369/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/114#issuecomment-51151013
Go to
http://ddf3c3a987908e09f035-e0310aeee578bb7e835ae22ad00e2123.r47.cf5.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/114#issuecomment-51151092
You can merge this Pull Request by running:
git pull https://github.com/jclouds/jclouds-site apachecon-eu
Or you can view, comment on it, or merge it online at:
https://github.com/jclouds/jclouds-site/pull/118
-- Commit Summary --
* Add ApacheCon EU 2014 blog post
-- File Changes --
@nacx @zack-shoylev Please edit your blurbs as appropriate.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/118#issuecomment-51152352
[jclouds-site-pull-requests
#370](https://jclouds.ci.cloudbees.com/job/jclouds-site-pull-requests/370/)
SUCCESS
This pull request looks good
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/118#issuecomment-51152566
Go to
http://7465fc100b9f3e2420a9-4f4bac9bb1a7dbe4741a17d8142cfa51.r13.cf5.rackcdn.com/
to review your changes.
---
Reply to this email directly or view it on GitHub:
https://github.com/jclouds/jclouds-site/pull/118#issuecomment-51152675
64 matches
Mail list logo
