[prev in list] [next in list] [prev in thread] [next in thread]
List: asterisk-dev
Subject: Re: [asterisk-dev] Branching in the Testsuite
From: Kevin Harwell <kharwell () digium ! com>
Date: 2018-03-16 19:19:47
Message-ID: CAM-yhn=gyugroZrZpYCF9mCVODN8jAupkoZ7K=d6rpmELNwrkg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Update!
Branching now exists in the Asterisk testsuite. Moving forward, when
creating a test for the testsuite you should no longer need to include the
Asterisk versioning information. Just write the test against the
appropriate branch. Also, when uploading a patch to gerrit, please be sure
to cherry pick the test to any other applicable branches.
As well when executing the testsuite be sure to run it against the correct
Asterisk branch. Otherwise you will receive failures due to some tests not
being supported on that branch.
For each new release of Asterisk a tag is created in the Testsuite for the
previous release's branch, which is then deleted (the branch that is).
Note, in order to minimize the number of tags, especially the number of
tags potentially pointing to the same commit, only one final tag is created
for a single release branch. This tag will have the same version number as
the last Asterisk version released for that branch.
Lastly, as mentioned in another post a "legacy" branch now exists that
maintains the state of the testsuite just prior to adding in branching.
This exists for historical purposes and new tests should *not* go into it.
Thanks!
On Fri, Dec 15, 2017 at 10:59 AM, Kevin Harwell <kharwell@digium.com> wrote:
> Greetings,
>
> We're thinking about adding a branching system to the Asterisk Testsuite.
> Each branch would be named the same as, and correspond to, an Asterisk
> branch. So for instance the following branches would probably be created:
>
> 13, 14, 15
>
> For each release of Asterisk we will also create a tag in the Testsuite
> that corresponds to that release's tag. That way someone could checkout
> both tags for easy testing
>
> Other advantages? Most all, if not all, the current versioning stuff found
> in the Testsuite could go away, or be safely ignored moving forward. The
> versioning has become a bit cumbersome especially when you have to make a
> backward incompatible change to a test. Moving the version control out of
> the Testsuite and into a version control system should alleviate the need
> for this moving forward.
>
> Please let us know your thoughts and considerations on moving forward with
> this model. Especially any potential pitfalls or problems you might see
> with it.
>
> Thanks!
>
> --
>
> Kevin Harwell
> Digium, Inc. | Software Developer
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
> Check us out at: http://digium.com & http://asterisk.org
>
>
--
Kevin Harwell
Digium, Inc. | Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: http://digium.com & http://asterisk.org
[Attachment #5 (text/html)]
<div dir="ltr">Update!<div><br></div><div>Branching now exists in the Asterisk \
testsuite. Moving forward, when creating a test for the testsuite you should no \
longer need to include the Asterisk versioning information. Just write the test \
against the appropriate branch. Also, when uploading a patch to gerrit, please be \
sure to cherry pick the test to any other applicable \
branches.</div><div><br></div><div>As well when executing the testsuite be sure to \
run it against the correct Asterisk branch. Otherwise you will receive failures due \
to some tests not being supported on that branch.</div><div><br></div><div>For each \
new release of Asterisk a tag is created in the Testsuite for the previous \
release's branch, which is then deleted (the branch that is). Note, in order to \
minimize the number of tags, especially the number of tags potentially pointing to \
the same commit, only one final tag is created for a single release branch. This tag \
will have the same version number as the last Asterisk version released for that \
branch.</div><div><br></div><div>Lastly, as mentioned in another post a \
"legacy" branch now exists that maintains the state of the testsuite just \
prior to adding in branching. This exists for historical purposes and new tests \
should *not* go into it.</div><div><br></div><div>Thanks!</div></div><div \
class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 15, 2017 at 10:59 AM, \
Kevin Harwell <span dir="ltr"><<a href="mailto:kharwell@digium.com" \
target="_blank">kharwell@digium.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr">Greetings,<div><br></div><div>We're \
thinking about adding a branching system to the Asterisk Testsuite. Each branch would \
be named the same as, and correspond to, an Asterisk branch. So for instance the \
following branches would probably be created:</div><div><br></div><div>13, 14, \
15</div><div><br></div><div>For each release of Asterisk we will also create a tag in \
the Testsuite that corresponds to that release's tag. That way someone could \
checkout both tags for easy testing</div><div><br></div><div>Other advantages? Most \
all, if not all, the current versioning stuff found in the Testsuite could go away, \
or be safely ignored moving forward. The versioning has become a bit cumbersome \
especially when you have to make a backward incompatible change to a test. Moving the \
version control out of the Testsuite and into a version control system should \
alleviate the need for this moving forward.</div><div><br></div><div>Please let us \
know your thoughts and considerations on moving forward with this model. Especially \
any potential pitfalls or problems you might see with \
it.</div><div><br></div><div>Thanks!</div><span class="HOEnZb"><font \
color="#888888"><div><br></div><div>-- <br><div \
class="m_-8822759529212355755gmail_signature" data-smartmail="gmail_signature"><div \
dir="ltr"><pre style="padding:2px;border:1px solid \
rgb(114,99,77);background-color:rgb(238,238,238);color:rgb(0,0,0);overflow:auto">Kevin \
Harwell Digium, Inc. | Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: <a href="http://digium.com" target="_blank">http://digium.com</a> \
& <a href="http://asterisk.org" \
target="_blank">http://asterisk.org</a></pre></div></div> </div></font></span></div>
</blockquote></div><br><br clear="all"><div><br></div>-- <br><div \
class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><pre \
style="padding:2px;border:1px solid \
rgb(114,99,77);background-color:rgb(238,238,238);color:rgb(0,0,0);overflow:auto">Kevin \
Harwell Digium, Inc. | Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at: <a href="http://digium.com" target="_blank">http://digium.com</a> \
& <a href="http://asterisk.org" \
target="_blank">http://asterisk.org</a></pre></div></div> </div>
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic