<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Rod Dorman escribió:
<blockquote cite="mid:1234749205.20091007175043@polylogics.com"
type="cite">
<pre wrap="">On Wednesday, October 7, 2009, 17:47:05, Rod Dorman wrote:
</pre>
<blockquote type="cite">
<pre wrap="">...
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap=""> * Minor - This number reflects an update with bug fixes only.
* Patch - This number will be optionally used to reflect trivial
changes to a patch release. This is most often used for
security updates.
</pre>
</blockquote>
</blockquote>
<pre wrap="">I'm curious about the need for both 'Minor' and 'Patch'
What would be an example of a "trivial" change that couldn't just bump
the 'Patch' level?
</pre>
</blockquote>
<pre wrap=""><!---->
Sigh... today is just not my day. I meant of course bump the 'Minor'
level.
</pre>
</blockquote>
Well according to what I've seen in asterisk versions, the differences
between 'Minor' and 'Patch', are that the 'Minor' includes a whole
bunch of fixes that resolve some bugs in a given amount of time
(several weeks usually), on the normal bug fixing release process.
'Patch' is just for a quick "urgent" fix or to introduce a security fix
(the ones named AST-YYYY-XXX). It makes sense, because usually only one
patch is made to the code on that kind of quick release.<br>
<br>
Cheers,<br>
<pre class="moz-signature" cols="72">--
Ing. Miguel Molina
Grupo de Tecnología
Millenium Phone Center
</pre>
</body>
</html>