Hello everyone,
TL;DR: LAVA development and deployment infrastructure will be moving to git over the course of this month. The expected cut off date is August 18th.
We are starting the migrating all of the LAVA source code from bzr to git today. We planned this to happen in the least-desruptive way possible, so this will be done in a phases.
The plan is the following:
----------------8<----------------8<----------------8<-----------------
1) mirror current bzr branches into git.
So the first step is to make the contents of the existing bzr repos on git. This is done, and all LAVA components are available at git.linaro.org. Those repositories contain the contents of their bzr counterparts as of today, and will be updated again when we discontinue bzr.
This step is already done.
2) update deployment infrastructure to use git
lava-deployment-tool and lava-manifest will be branched already in their git repositories updated to pull code for the other components from git instead of bzr. This will be tested on staging, including upgrading from a bzr-based deployment to a git-based one.
lava-lab (the repository where we maintain the salt configuration for the Linaro Cambridge lab) will also be switched to git at this point.
Up until this phase is completed, bug fixes and updates to the official production site will still be done from bzr.
3) final bzr cut off and move to git
When we are satisfied with the deployment from git branches, we will finally discontinue bzr.
lava-deployment-tool and lava-manifest "deploy-from-git" branches will be merged into the respective master branches.
All other components will be synced from bzr to git one last time.
At this point the bzr branches on Launchpad will be officially deprecated and will probably not receive any more updates (so that getting the latest version on bzr continues to be possible).
Development moves to git.linaro.org.
We will continue using Launchpad for bug management.
This is expected to be done by August the 18th.
----------------8<----------------8<----------------8<-----------------
Please feel free to voice any concerns or questions regarding this change.
On Thu, Sep 05, 2013 at 05:38:33PM -0300, Antonio Terceiro wrote:
Hello everyone,
TL;DR: LAVA development and deployment infrastructure will be moving to git over the course of this month. The expected cut off date is August 18th.
[...]
This is expected to be done by August the 18th.
Of course, I meant *September* the 18th. :-)
On 5 Sep 2013, at 21:38, Antonio Terceiro antonio.terceiro@linaro.org wrote:
Hello everyone,
TL;DR: LAVA development and deployment infrastructure will be moving to git over the course of this month. The expected cut off date is August 18th.
Now that's what I call aggressive scheduling! :D
Dave
We are starting the migrating all of the LAVA source code from bzr to git today. We planned this to happen in the least-desruptive way possible, so this will be done in a phases.
The plan is the following:
----------------8<----------------8<----------------8<-----------------
- mirror current bzr branches into git.
So the first step is to make the contents of the existing bzr repos on git. This is done, and all LAVA components are available at git.linaro.org. Those repositories contain the contents of their bzr counterparts as of today, and will be updated again when we discontinue bzr.
This step is already done.
- update deployment infrastructure to use git
lava-deployment-tool and lava-manifest will be branched already in their git repositories updated to pull code for the other components from git instead of bzr. This will be tested on staging, including upgrading from a bzr-based deployment to a git-based one.
lava-lab (the repository where we maintain the salt configuration for the Linaro Cambridge lab) will also be switched to git at this point.
Up until this phase is completed, bug fixes and updates to the official production site will still be done from bzr.
- final bzr cut off and move to git
When we are satisfied with the deployment from git branches, we will finally discontinue bzr.
lava-deployment-tool and lava-manifest "deploy-from-git" branches will be merged into the respective master branches.
All other components will be synced from bzr to git one last time.
At this point the bzr branches on Launchpad will be officially deprecated and will probably not receive any more updates (so that getting the latest version on bzr continues to be possible).
Development moves to git.linaro.org.
We will continue using Launchpad for bug management.
This is expected to be done by August the 18th.
----------------8<----------------8<----------------8<-----------------
Please feel free to voice any concerns or questions regarding this change.
-- Antonio Terceiro Software Engineer - Linaro http://www.linaro.org _______________________________________________ linaro-validation mailing list linaro-validation@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-validation
Hello Antonio,
On Thu, 5 Sep 2013 17:38:33 -0300 Antonio Terceiro antonio.terceiro@linaro.org wrote:
Hello everyone,
TL;DR: LAVA development and deployment infrastructure will be moving to git over the course of this month. The expected cut off date is August 18th.
[]
on git. This is done, and all LAVA components are available at git.linaro.org. Those repositories contain the contents of their bzr counterparts as of today, and will be updated again when we discontinue bzr.
[]
Development moves to git.linaro.org.
I guess, it makes sense to clarify server issue. I see that lava repos indeed were imported to git.linaro.org, but infrastructure supporting git development is (reviews, etc.) is so far available only on staging.git.linaro.org . I just checked with Milo, and he says that lava repos from staging get automatically synced to git.linaro.org, but well, worth all these details to be mentioned explicitly.
On Tue, Sep 17, 2013 at 12:39:07PM +0300, Paul Sokolovsky wrote:
Hello Antonio,
On Thu, 5 Sep 2013 17:38:33 -0300 Antonio Terceiro antonio.terceiro@linaro.org wrote:
Hello everyone,
TL;DR: LAVA development and deployment infrastructure will be moving to git over the course of this month. The expected cut off date is August 18th.
[]
on git. This is done, and all LAVA components are available at git.linaro.org. Those repositories contain the contents of their bzr counterparts as of today, and will be updated again when we discontinue bzr.
[]
Development moves to git.linaro.org.
I guess, it makes sense to clarify server issue. I see that lava repos indeed were imported to git.linaro.org, but infrastructure supporting git development is (reviews, etc.) is so far available only on staging.git.linaro.org . I just checked with Milo, and he says that lava repos from staging get automatically synced to git.linaro.org, but well, worth all these details to be mentioned explicitly.
Sure. So, to clarify: the LAVA team will _actually_ work on staging.git.linaro.org (gitolite+gitweb) + staging.review.linaro.org (gerrit) as a dogfooding excercise.
The repositories on git.linaro.org will be kept up to date by a cron job until the new git infrastructure becomes the main one. So to the "outside world", git.linaro.org will be the official source of git hosting for LAVA as it is for the rest of the Linaro projects.
linaro-validation@lists.linaro.org
-
Antonio Terceiro -
Dave Pigott -
Paul Sokolovsky