On Monday, we created Xen 4.8 RC1 and will release a new release candidate every week, until we declare a release candidate as the final candidate and cut the Xen 4.8 release. We will also hold a Test Day every Friday for the release candidate that was released the week prior to the Test Day. Note that RC’s are announced on the following mailing lists: xen-announce, xen-devel and xen-users. This means we will have Test Days on October 7th, 14th, 21st and 28th.
Your testing is still valuable on other days, so please feel free to send Test Reports as outlined below at any time.
Getting, Building and Installing a Release Candidate
Release candidates are available from our git repository at
git://xenbits.xenproject.org/xen.git (tag 4.8.0-<rc>)
rc3, etc. and as tarball from
Detailed build and Install instructions can be found on the Test Day Wiki.
Testing new Features, Test and Bug Reports
You can find Test Instructions for new features on our Test Day Wiki and instructions for general tests on Testing Xen. The following pages provide information on how to report successful tests and how to report bugs and issues.
Attached is the final, complete Xen Trademark Policy as approved by the Xen Advisory Board and updated with your comments. Please feel free to offer any additional feedback you have as this document is meant to “live” as Xen continues to evolve.
Xen Trademark Policy June 08 in pdf
Also, the FIT discussed in the document is being worked on by the Advisory Board and I will publish the latest proposal shortly after it is reviewed by the Advisory Board.
The updated Xen Trademark Policy based on your feedback is almost complete and ready for final community inspection; however, I did get a response from Citrix about the decision to restrict usage of the Xen name in products. Please feel free to add comments or send me any questions. Thanks.
The comment from Citrix legal is as follows:
Citrix, in conjunction with the Xen AB, seeks to protect the trademarks associated with the open source Xen® hypervisor in order to both strengthen the public’s identification of the Xen marks and prevent the widespread and unregulated use that can sometimes lead to trademark genericide. This is for the benefit of all those in the Xen community who distribute and contribute to the open source project, and not just for the benefit of Citrix. It is for these reasons that the Xen Trademark Policy was originally put forward.
With respect to the limited restriction on product names combining “Xen” with another name, Citrix believes this restriction is in keeping with XenSource, Inc’s longstanding use of “Xen” in the names of the company (“XenSource™”) and its flagship product (“XenServer™”), which is now marketed by Citrix. Citrix believes, and hopes that the community understands, that use of other Xen-combined names might confuse potential users of Citrix-sourced products as to the source of a particular product or service. Since all Xen-based commercial products on the market today (of which Citrix is aware) from other vendors are all non-Xen branded, Citrix believes that this is the appropriate time to clarify this issue.
For example, an ISV may create a service for registering servers running Xen and decide to call the service “XenRegister”. A reasonable IT consumer could be confused and assume that the XenRegister service is sourced by XenSource and Citrix. Instead, the ISV could call their service, for example, “VM Registration for the Xen® hypervisor” or “MegaRegister™ for Xen®,” or any other name which is in keeping with the Xen Trademark Policy and does not reasonably confuse an IT consumer as to its source.
Ultimately, the Xen Trademark Policy benefits all those who use or assist in the development of the Xen® hypervisor, in part by maintaining the value of the Xen Marks. Citrix must police the marks in accordance with the Policy and in conjunction with the Xen AB in order for everyone to see value in their use as product identifiers. Otherwise, the trademark can become a generic term (see escalator or aspirin in the U.S.) at which point anyone could call their hypervisor “xen” regardless of the source of the hypervisor.