Skip to content
This repository was archived by the owner on Mar 25, 2018. It is now read-only.

Updated to jclouds 1.6.1#142

Closed
etoews wants to merge 1 commit into
jclouds:masterfrom
rackerlabs:jclouds-1.6.1
Closed

Updated to jclouds 1.6.1#142
etoews wants to merge 1 commit into
jclouds:masterfrom
rackerlabs:jclouds-1.6.1

Conversation

@etoews

@etoews etoews commented Jun 24, 2013

Copy link
Copy Markdown
Member

No description provided.

@buildhive

Copy link
Copy Markdown

jclouds » jclouds.github.com #38 SUCCESS
This pull request looks good
(what's this?)

@abayer

abayer commented Jun 24, 2013

Copy link
Copy Markdown
Member

While you're at it, any chance you could handle https://issues.apache.org/jira/browse/JCLOUDS-143?

@gaul

gaul commented Jun 24, 2013

Copy link
Copy Markdown
Member

+1

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The 1.6.1 docs are currently being built, by the way...

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@etoews

etoews commented Jun 24, 2013

Copy link
Copy Markdown
Member Author

@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.

@etoews

etoews commented Jun 24, 2013

Copy link
Copy Markdown
Member Author

@demobox Is there an ETA on the Javadoc?

@etoews

etoews commented Jun 24, 2013

Copy link
Copy Markdown
Member Author

Split into:
#143
#144

@etoews etoews closed this Jun 24, 2013
@etoews etoews deleted the jclouds-1.6.1 branch June 24, 2013 21:43
@mattstep

Copy link
Copy Markdown
Member

Always ok to have multiple commits in the same PR ;)

@etoews

etoews commented Jun 24, 2013

Copy link
Copy Markdown
Member Author

Heh. That would have been a bit easier.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants