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 che
On Mon, Jan 22, 2018 at 12:41 PM, Kevin Harwell wrote:
> I'm getting ready to start the process of branching the testsuite. I'm
> going to give a basic overview here of what I'm going to do, so as things
> get posted on gerrit people will have some idea as to what is coming, and
> why.
>
> To sta
I'm getting ready to start the process of branching the testsuite. I'm
going to give a basic overview here of what I'm going to do, so as things
get posted on gerrit people will have some idea as to what is coming, and
why.
To start I'm not going to touch the current master branch. This will be
re
I went ahead and created an issue to track this:
https://issues.asterisk.org/jira/browse/ASTERISK-27492
Feel free to add comments or suggestions on the issue as well.
On Fri, Dec 15, 2017 at 10:59 AM, Kevin Harwell wrote:
> Greetings,
>
> We're thinking about adding a branching system to the A
On Mon, Dec 18, 2017 at 9:01 AM, Corey Farrell wrote:
> Sounds good. So after this is done am I correct that when my review
> against asterisk 13 is approved jenkins will 'gate' using the 13 branch of
> testsuite?
>
Correct.
> Will the testsuite also get minor branches (like 13.19)?
>
Not quit
Sounds good. So after this is done am I correct that when my review
against asterisk 13 is approved jenkins will 'gate' using the 13 branch
of testsuite? Will the testsuite also get minor branches (like 13.19)?
On 12/15/2017 03:24 PM, George Joseph wrote:
On Fri, Dec 15, 2017 at 10:56 AM,
On Fri, Dec 15, 2017 at 10:56 AM, Corey Farrell wrote:
> It would be nice to strip out some/most of the per version conditionals in
> tests. The need to always cherry-pick changes is the only pitfall I see
> with your proposal. If a test never had per version differences then the
> cherry-pick
It would be nice to strip out some/most of the per version conditionals
in tests. The need to always cherry-pick changes is the only pitfall I
see with your proposal. If a test never had per version differences
then the cherry-pick is trivial amount of extra work, but for tests with
differenc
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
