Already mentioned, but I think this is more helpful in the isolated case of chef, which wasn't labs, and the ideal case of labs where something is promoted within a few weeks to months of it being started.
The crap-case of many labs providers is that we will be importing random history of more than a year (see openstack-swift and soon azurecompute). I don't see much value in that, and figured I should voice this clearly. In other words, in some cases cure is worse than the disease. -A On Wed, Oct 8, 2014 at 9:28 AM, Ignasi Barrera <n...@apache.org> wrote: > So I've written down the steps I followed in this page on the wiki > (note that I reference the original tutorial but the commands are > slightly different): > https://wiki.apache.org/jclouds/PromoteProvider > > The result can be checked out at: > https://github.com/nacx/jclouds/tree/jclouds-chef-merge > > If you find the procedure OK, we can establish it as the way to > promote providers. > > On 8 October 2014 18:21, Adrian Cole <adrian.f.c...@gmail.com> wrote: >> OK so unless we have nothing better to do but try to preserve the >> history of maintenance of openstack-swift between the time it was >> written, the few minor changes, and boatload of maintenance, I'd >> suggest we just merge the following. >> >> openstack-swift out of labs >> https://github.com/jclouds/jclouds/pull/563 - master >> https://github.com/jclouds/jclouds/pull/564 - 1.8.x >> >> -A >> >> On Wed, Oct 8, 2014 at 7:38 AM, Adrian Cole <adrian.f.c...@gmail.com> wrote: >>> Wires crossed! >>> >>> Ok. I will raise a source import pull request for openstack-swift and >>> friends. I suppose I could simultaneously for 1.8.x just wait until we are >>> ready to merge that. >>> >>> -A >>> >>> On Oct 8, 2014 7:31 AM, "Ignasi Barrera" <ignasi.barr...@gmail.com> wrote: >>>> >>>> The same happens to chef. I've tried to find a way to keep history, >>>> but I haven't found any. Take into account that moving to the main >>>> repo also implies a "restructure" of the project. In the case of Chef, >>>> the "core" folder is moved to "apis", and the "enterprisechef" one to >>>> "providers". >>>> >>>> On 8 October 2014 16:21, Andrew Phillips <aphill...@qrmedia.com> wrote: >>>> >> While this wouldn't retain history, we can cite the >>>> >> jclouds-labs-openstack repo for history. Other ideas welcome. >>>> > >>>> > >>>> > Sounds good to me - what are we doing with jclouds-chef, which is also >>>> > undergoing a similar merge at this time? >>>> > >>>> > Would filter-branch [1] help in preserving history in some way? Could we >>>> > "convert" the repo to a branch on master and submit a PR to merge that? >>>> > >>>> > ap >>>> > >>>> > [1] http://git-scm.com/docs/git-filter-branch
