Re: [Xen-API] XCP 1.5 Release Date

[<admin@xxxxxxxxxxx>]

Will there be a build of XenCenter released that natively understands XCP
version numbers, or will XCP users still need to manually hack the version
numbers?

Also, please post a link to "Project Swizzle".

-----Original Message-----
From: xen-api-bounces@xxxxxxxxxxxxx [mailto:xen-api-bounces@xxxxxxxxxxxxx]
On Behalf Of Mike McClurg
Sent: Tuesday, August 28, 2012 12:50 PM
To: lars.kurth@xxxxxxx
Cc: 'community.manager@xxxxxxx'; Tom Putnam; xen-api@xxxxxxxxxxxxx
Subject: Re: [Xen-API] XCP 1.5 Release Date

Hi Tom,

I've summarized your questions here:

> When is XCP 1.5 release date?

Because we're so close to releasing XCP 1.6, we are considering skipping
the final release of XCP 1.5. We weren't able to finish "Project
Swizzle" in time for XCP 1.5, meaning that it takes a significant bit of
work to rebrand XenServer 6.0 to XCP 1.5. Swizzle has finished in time
for XCP 1.6, which means that we don't need to perform any extra work to
produce XCP 1.6.

> When will dom0 be 64-bit?

We don't have definite plans for this. Typically the only reason to want
a 64-bit dom0 is for driver compatibility, though. If you really need a
64-bit dom0, and you're not afraid to do some hacking, you can try
installing Xapi on Debian or Ubuntu
(http://wiki.xen.org/wiki/XAPI_on_Ubuntu). That wiki needs some
updating, but it shows the general steps required.

Mike

On 24/08/12 01:21, Lars Kurth wrote:
> Tom,
> I forwarded the question to the xen-api list which is monitored by the
> project lead
> Regards
> Lars
> 
> On 23/08/2012 15:45, Tom Putnam wrote:
>>
>> Hi there.
>>
>>  
>>
>> So far we are having a good experience with XCP.
>>
>>  
>>
>> A few questions:
>>
>>  
>>
>> .         When is the release date for XCP 1.5?
>>
>> .         Also in looking at the XCP roadmap, it is unclear on when
>> dom0 will be 64-bit.
>>
>>  
>>
>> Thanks!
>>
>>  
>>
>> Tom Putnam
>>
>> ------------------------------------------------------------------------
>> This email message is for the sole use of the intended recipient(s)
>> and may contain confidential information.  Any unauthorized review,
>> use, disclosure or distribution is prohibited.  If you are not the
>> intended recipient, please contact the sender by reply email and
>> destroy all copies of the original message.
>> ------------------------------------------------------------------------
> 


_______________________________________________
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