Hello everyone,

TL;DR: as announced previously [1], since today LAVA development happens
on git.

Some points I would like to highlight:

- Please do not send bzr merge proposals against the old bzr
  repositories on Launchpad. In the next days those repositories will be
  closed down (assuming that's at all possible - any tips appreciated)
  to make it impossible for people to send those.

- The procedure for submitting changes to LAVA is now using the gerrit
  instance at staging.review.linaro.org, which should be available as
  review.linaro.org at some point in the future. As mentioned
  previously, we are dogfooding the system before providing it as an
  official service for the wider community, so bear with me and please
  let us know of any problems or questions you might have.

  Documentation for staging.review.linaro.org is available at:
  https://wiki.linaro.org/Platform/LAVA/Infrastructure/StagingReview

- the source for source code is git.linaro.org, under the lava/
  namespace.

  As we already discussed, the LAVA team will be actually using
  staging.git.linaro.org as part of the aforementioned dogfooding
  exercise. However we configured sync on push in the lava repositories
  so that git.linaro.org and staging.git.linaro.org will always contain
  exactly the same code.

- Launchpad is still used for bug management. Please continue submitting
  bugs there.

- Unrelated to the move to git, you will notice two important changes in
  LAVA that I think it's useful to mention:

  The first change is that now we have a new theme[2] which IMO makes
  LAVA look a lot nicer. It's not a designer's job, but is an
  improvement. ;-)

  The second change is that now every LAVA instance hosts full
  documentation _generated from the actual code it is running_, linked
  from the "Documentation" link in the top menu[3]. It's still the same
  old documentation we had before on .readthedocs.org, but this is just
  the first visible step of the effort the LAVA team is putting in the
  documentation area. Expect exciting news about this in the future.

1. 
http://lists.linaro.org/pipermail/linaro-validation/2013-September/002067.html
2. see it for yourself at http://validation.linaro.org/
3. e.g. http://validation.linaro.org/static/docs/

Cheers,

-- 
Antonio Terceiro
Software Engineer - Linaro
http://www.linaro.org

Attachment: signature.asc
Description: Digital signature

_______________________________________________
linaro-validation mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/linaro-validation

Reply via email to