Take a look at PR 755 at https://github.com/apache/incubator-brooklyn/pull/755.
Each commit performs the appropriate rename on a single project, and their dependent projects. As I am approaching the core packages, the list of PRs should be cleared first, but I believe all of my commits there won't encounter conflicts. I will continue with the CAMP-related projects for today, which seem to not be affected by pull requests. Ciprian On Wednesday 22 July 2015 23:50:35 Aled Sage wrote: > +1 to renaming the packages. > > Whether the next release is then 0.8.0 or 1.0.0 is up for debate. > > With a concerted effort, I'm sure we can significantly reduce the PR > queue. I suggest we do the package renames early next week - giving us a > few days for merging PRs. Focused/localised changes like renaming > packages in the REST api could be done before then. > > Aled > > On 22/07/2015 18:16, Hadrian Zbarcea wrote: > > Hi, > > > > It looks like it's a bit controversial if the package names update is > > required or required for graduation. Rob Vesse says that in Jena they > > didn't do it for graduation, but they still did it when moved to the > > next major release. > > > > Since we are before the 1.0.0 release, unless we want to keep the > > brooklyn.* packages for ever, I would suggest doing the package update > > to org.apache.brooklyn.* sooner vs than later and plan to release > > 0.8.0 shortly after. > > > > It looks like it's not easy to shorten the PR queue, so I would favour > > a piecemeal approach, even if it would require redoing some of the > > PRs. I suspect that with the right granularity, we could avoid > > conflicts most of the time. > > > > Thoughts? > > Hadrian
