<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 08/30/2012 01:47 PM, Vijay Bellur wrote:<br>
<blockquote>><br>
> <a class="moz-txt-link-freetext" href="http://bits.gluster.com/pub/gluster/glusterfs/3.3.1qa2/">http://bits.gluster.com/pub/gluster/glusterfs/3.3.1qa2/</a><br>
><br>
>
<a class="moz-txt-link-freetext" href="http://bits.gluster.com/pub/gluster/glusterfs/src/glusterfs-3.3.1qa2.tar.gz">http://bits.gluster.com/pub/gluster/glusterfs/src/glusterfs-3.3.1qa2.tar.gz</a><br>
><br>
> This release is made off v3.3.1qa2<br>
<br>
Hi Vijay,<br>
<br>
if you spin RPMs from these, could you make sure that you make
them upgradable with non-qa/beta bits? The easiest to get that is
to create a release with a preceding "0.", something like
glusterfs-3.3.1-0.qa2. A GA release starts with 3.3.1-1 and will
therefore be an update to the qa release.<br>
<br>
I'm not sure how/if this can be done with auto-tools though :-/<br>
<br>
Thanks,<br>
Niels<br>
</blockquote>
<br>
I think it would be great to take this comment in account, because
for the moment upgrading from qa -> beta is quite difficult in
environment like puppet.<br>
Yum/rpm will always think qa > beta and not upgrade the packages.<br>
<br>
-- <br>
Thomas<br>
</body>
</html>