Hi All, I just deleted a whole bunch of documentation on Publishing Javadoc [1] and replaced it with a script. This came out of lots of good work with AP on JCLOUDS-147.
I would very much like to see us give the same treatment to Releasing jclouds [3]. Currently releasing jclouds is very complicated, manual, and error prone. There are also lots of assumptions baked into the process that you don’t discover unless it’s the first time you’re doing it or you’re doing it from a new laptop. Releasing jclouds and validating it should be a trivial thing to do. It shouldn’t require much time or thought to do. We run some scripts, click a few buttons on repository.apache.org, validate/test it with more scripts, and release it. If our users need a minor release or even just a patch release, we should be able to provide it to them quickly and easily. For the 1.7.4 release in mid-July, I propose that we have at least 2 people release jclouds. It should be released from a completely fresh environment, e.g. a newly created VM, that both people have access to. These 2 people work together in the VM and over IRC to create a script(s) to release jclouds. I expect that we won’t be able to script the entire process the first time around. That’s okay, it may take us more than one release to get it right and repeatable. I ask there to be 2 people because I found the release process so error prone that trying to create a script and release it at the same time felt impossible. Having another set of eyes and hands is essential. I’m happy to volunteer as 1 of those 2 people. Everett [1] https://wiki.apache.org/jclouds/Publishing%20Javadoc [2] https://issues.apache.org/jira/browse/JCLOUDS-147 [3] https://wiki.apache.org/jclouds/Releasing%20jclouds
