On Tue, Jul 29, 2014 at 01:52:41AM +0000, Everett Toews wrote: > 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.
Sorry that this is so painful, but thanks for describing the pros and cons! > 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 Agree with all these points, especially the last one. Do we clearly communicate to users what labs means today? > Cons: > > * Longer build times > > What have I missed? We will lose git history if we migrate repositories; people will have to consult the old repositories. > 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. +1, I strongly support bringing labs back to the main repo. We can continue to have a separate labs directory if we want to continue to have some distinction. -- Andrew Gaul http://gaul.org/
