Re: [Xen-API] Xapi Project 2.0 release

[Olivier Lambert <lambert.olivier@xxxxxxxxx>]

Hi Jon,

XO team reporting :)

I think for a better community visibility, GitHub is the right way.
You can tag any issue with anything you like, and thus create simple
yet powerful workflows. Using the Xen wiki will sound more "closed".

As we discussed in the Hackathon, documentation is also really
important to catch people and really impulse a community. When I'll
have time, I'll probably create issues or create requests for this
doc.

Cheers,

--
Olivier
Xen Orchestra Project Leader
http://xen-orchestra.com

On Mon, Jun 2, 2014 at 2:59 PM, Jon Ludlam
<jonathan.ludlam@xxxxxxxxxxxxx> wrote:
> Hi all,
>
> It's about time we had a release!
>
> There has been a huge amount of effort been spent over the last year or
> so since we joined the Linux Foundation, and we're almost at the point
> where the master branch of the xapi-project repositories can be used to
> manage VMs in several different environments. So the main goal of this
> release is that it works without source change on XenServer, CentOS 6.5
> and Ubuntu 14.04. Note that this will be a source only release, as with
> standard xen-project releases.
>
> What we need to do is agree as a community what we need to do before we
> hit the release button. We had a good starting discussion at the Xen
> Hackathon last week, which I'll summarise here:
>
> * Needs to pass 'exercise.sh' tests on Ubuntu 14.04 and CentOS 6.5 (via
> buildroot packages).
> * On XenServer, we can exploit the Citrix internal tests (nightly and
> stress), which need to pass with 'reasonable' rates.
> * All OCaml libraries must be available in opam - either through
> xapi-project/opam-repo-dev or (preferably) the standard opam repository.
> * Need to be able to bypass xcp-networkd taking over the management of
> the networking on the host.
> * Documentation! We need at least installation, basic usage, and how to
> contribute, including build instructions.
>
> So, if anyone else has any suggestions for what needs to be done before
> release, please reply and we'll gather together a list of requirements.
>
> Also, we'll need to track the todo list. Anybody have any preference for
> where to do this? wiki.xenproject.org? Github issues?
>
> Cheers,
>
> Jon
>
>
> _______________________________________________
> Xen-api mailing list
> Xen-api@xxxxxxxxxxxxx
> http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api

_______________________________________________
Xen-api mailing list
Xen-api@xxxxxxxxxxxxx
http://lists.xen.org/cgi-bin/mailman/listinfo/xen-api