asterisk users - Jun 2009 - SVN vs "Regular" Asterisk

Hi gang,

             Can someone shed some light on the pros and cons of working
with the SVN branches of Asterisk vs working in the 1.4 or 1.6 branches?
What branch does the SVN release roughly equate to?

 

 

TIA

Danny Nicholas

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20090601/2d74e3f7/attachment.htm

On Mon, Jun 1, 2009 at 12:02 PM, Danny Nicholas <danny at debsinc.com>
wrote:
> Hi gang,
>
> ???????????? Can someone shed some light on the pros and cons of working
> with the SVN branches of Asterisk vs working in the 1.4 or 1.6 branches?
> What branch does the SVN release roughly equate to?
What do you mean by 'working with'?

If you are developing asterisk code, as in changes to the source code
of asterisk, the benefits are that you know whether:
a) anybody else has already made the changes you want to make
b) your changes merge successfully with the latest code

If you plan to make your changes available to the community, you are
better off developing against SVN, as that is where your patches will
eventually have to be applied.

If you are just compiling and using asterisk, the benefit is that you
are getting the very latest features, including bug fixes that may not
yet be in a release. By definition, SVN is ahead of the next release.
You can answer for yourself what SVN equates to by navigating the
tree, but I would characterize it as 1.6.2plus

On Mon, 2009-06-01 at 11:02 -0500, Danny Nicholas wrote:
> What branch does the SVN release roughly equate to?
Let me see if I can help clear things up here...

Imagine, if you will, a tree growing in a forest.  It has a nice sturdy
trunk, and a few branches.  As time goes on, the tree gets taller (from
the top of the tree), but the branches stay at the same height relative
to the ground.

Now that you have this image in your head, let me explain a bit about
Subversion and Asterisk development.  In Asterisk, developers add new
features to the trunk of SVN.  This changes on an almost daily basis,
and always contains the very latest changes to Asterisk.  You can check
out the trunk of Asterisk by typing "svn co
http://svn.digium.com/svn/asterisk/trunk".

In addition to the trunk, our SVN repository has branches as well.
There's a branch for 1.4, one for 1.6.0, one for 1.6.1, etc.  Along
these branches, we try to only apply bug fixes and not new features.
Tarball releases of Asterisk are made from these branches, not from the
trunk. So, for example, the only differences between 1.6.0.8 and 1.6.0.9
would be bug fixes.  (From time to time a new feature will be backported
if it helps to solve an existing bug, but this is a rare exception to
the rule.)  So, let's look at the 1.6.0 branch for a minute.  If you
were to check out the 1.6.0 branch using Subversion ("svn co
http://svn.digium.com/svn/asterisk/branches/1.6.0"), you'd essentially
end up with 1.6.0.9 plus any bug fixes that have been applied since the
1.6.0.9 release.  

Does that make sense?



-- 
Jared Smith
Training Manager
Digium, Inc.