One of the things that quickly becomes apparent when doing a release is that having so many repos makes it excruciatingly complicated to do a release. On a separate note, it also makes it very difficult to refactor jclouds core code.
Seems like every time we chat about it in IRC everybody agrees that having so many repos is a serious pain point. Which is to say, no one is excited about having so many repos. I know there were reasons for splitting the main repo up in the first place but I think it’s time to revisit this. Here are the pros and cons as I see them. Pros: * Sane Maven parenting * Easier releases * Better visibility into all jclouds code when making changes to jclouds main repo code * Easier refactoring of jclouds main repo code that labs code depends on * Less chance of breaking a labs repo when upgrading a core dependency * Less CloudBees jobs * Less confusion from users about why the labs are separate repos Cons: * Longer build times What have I missed? Is it time for the labs repos to rejoin? We can figure out the mechanics of it after we’ve reached some kind of consensus. Thanks, Everett
