Hi Roy,
As you say, the project is young and we have not done our first release yet. In Citrix we run a lot of automated test on the code and also logo test the drivers so, with my community lead hat on, it makes sense to me to take advantage of that testing
and cut our first release from the tip changesets that the next fully tested Citrix binaries are built from. From that point on we may diverge, but staying close to Citrix releases is probably likely.
So, for the moment, I suggest you use the tips of the master branches. These have had a reasonable amount of test within Citrix and AFAIK by other folks on this list. I know of one backwards compatibility issue with a pre-Xen 4.4 hypervisor that Iâve
not had time to look at yet (to see if itâs actually a bug) but I donât know of any other problem with any released version of Windows. There is still an issue with installation of XENNET on Windows 10 (where the co-installer fails) but if thatâs not your
target environment then you should be fine.
Cheers,
Paul
From:
win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx]
On Behalf Of Roy Jenkins
Sent: 21 May 2015 10:33
To: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
Subject: [win-pv-devel] Release Strategy
Hi,
Our company are hoping to upgrade our production environments to use your Windows PV drivers, this is due to
limitations we found in the older GPLPV drivers.
I appreciate that this project is still young and in developmentâ,
but I noticed that your xenbits repository does not contain any tags or additional branches and was wondering if you have a release strategy in place. I did see that you include a changelog in your source, would you recommend building from the commit where
this file was last updated? Or do you consider the latest master revision to be most stable?
Thanks,
Roy
Zynstra is a private limited company registered in England and Wales (registered number 07864369). Our registered
office and Headquarters are at The Innovation Centre, Broad Quay, Bath, BA1 1UD. This email, its contents and any attachments are confidential. If you have received this message in error please delete it from your system and advise the sender immediately.
