Updated to jclouds 1.6.1#142
Conversation
|
jclouds » jclouds.github.com #38 SUCCESS |
|
While you're at it, any chance you could handle https://issues.apache.org/jira/browse/JCLOUDS-143? |
|
+1 |
There was a problem hiding this comment.
The 1.6.1 docs are currently being built, by the way...
There was a problem hiding this comment.
Can we document how that's done and get that onto something under jclouds.incubator.apache.org? I'll open a JIRA. Ideally, I'd like anything that's part of a release to be done as part of the release process, by the release manager (or at least overseen by the release manager), so that things like updating the site, getting the javadocs up, etc, doesn't lag.
There was a problem hiding this comment.
Can we document how that's done and get that onto something under jclouds.incubator.apache.org?
Absolutely! Let's get this hosted somewhere on Apache space as quickly as possible. There's nothing magical going on here - it's just generation of the Maven site, which includes the Javadocs. We should try to trim down the amount of what's generated to speed things up, then it's simply a matter of changing the POM to publish the site to wherever on Apache we should be hosting it.
|
@abayer I think that would have to be a separate commit. @mattstep Ya. I'm aware of the Javadoc link. I just wanted a valid link in there until @demobox has a chance to generate the 1.6.1 Javadoc. @mattstep Why separate commits? This is a PR for updating all of the docs to 1.6.1, not just the release notes. All changes for 1.6.1 should be together in a single commit. |
|
@demobox Is there an ETA on the Javadoc? |
|
Always ok to have multiple commits in the same PR ;) |
|
Heh. That would have been a bit easier. |
No description provided.