IMO 141 would be ideal. Using jclouds-project as the parent pom for all projects would be ideal. That should allow us to remove the "jclouds.version" property from all dependent projects and would make the release process much simpler.
I think 104 deviated from its initial purpose and become an issue to allow releasing the dependent projects independently from the main jclouds repo. That is something that could be useful, but if I am not wrong, we haven't needed that yet. So, if we can just implement 141 and make all repos inherit from jclouds-project, that would be great to unify how dependencies are configured in all repos (considering we always release all together). If needed, we can later open an explicit issue to allow a more fine-grained version configuration for the dependent modules, if we find we need that. WDYT? On 14 November 2013 22:13, Zack Shoylev <[email protected]> wrote: > Is there a short overview of what the current plan is? Is it 141? > ________________________________________ > From: Andrew Bayer [[email protected]] > Sent: Thursday, November 14, 2013 2:17 PM > To: [email protected] > Subject: Re: 1.7.0 scheduling > > I believe you're talking about > https://issues.apache.org/jira/browse/JCLOUDS-141 and > https://issues.apache.org/jira/browse/JCLOUDS-104? > > A. > > > On Thu, Nov 14, 2013 at 12:10 PM, Ignasi <[email protected]> wrote: > >> Sounds good to me. >> >> I'd really like to have the issue (don't remember the id) to configure the >> versioning in the "sub-repos" completed for 1.7. >> >> It has been done in several repos but not in all of them (at least >> jclouds-labs is still remaining), and I think it is important that we have >> a consistent configuration in all pom.xml. >> >> Initially Zack had the issue assigned (do you think you'll have some time >> to spend on it before releasing 1.7?) but I'll be happy to take it if >> needed. >> So with 1.6.3 aiming to be out next week, I'd like to put a target date on >> 1.7.0 - we really need to get that sucker out! I'm gonna tentatively plan >> to do the first RC on Monday, December 9th. >> >> There are a fair number of issues still open against 1.7.0 - see >> >> https://issues.apache.org/jira/browse/JCLOUDS-299?jql=project%20%3D%20JCLOUDS%20AND%20fixVersion%20%3D%20%221.7.0%22%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC >> >> But I've created new 1.7.1 and 1.8.0 versions in JIRA (and 1.6.4, for that >> matter), so we can move issues to those releases if appropriate (I just did >> for a few, will go through the remaining issues in more detail later >> today/tomorrow). It looks like the ones most likely not to get done for >> 1.7.0 are the remaining de-async related ones, and I'm fine with pushing >> that off to 1.8.0. >> >> Thoughts? >> >> A. >>
