[asterisk-dev] [Code Review]: Allow fine grained control over test version asterisk compatibility specification
Matthew Nicholson
reviewboard at asterisk.org
Thu Oct 13 10:05:19 CDT 2011
> On Oct. 13, 2011, 10:04 a.m., Matthew Nicholson wrote:
> > Thinking about this a little further, you should be able to specify a release range.
> >
> > - release:
> > from: 1.8
> > to: 10
> >
> > This corresponds to our current minversion and maxversion fields. I'll work on implementing that when I have some time.
I also think you should be able to exclude certain version groups too. Maybe with an 'excludeversions' property.
- Matthew
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/1454/#review4506
-----------------------------------------------------------
On Sept. 23, 2011, 7:53 a.m., Matthew Nicholson wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/1454/
> -----------------------------------------------------------
>
> (Updated Sept. 23, 2011, 7:53 a.m.)
>
>
> Review request for Asterisk Developers, Paul Belanger and mjordan.
>
>
> Summary
> -------
>
> This patch adds the ability to specify which versions of asterisk a test should be run on down to the SVN revision level.
>
>
> Diffs
> -----
>
> /asterisk/trunk/README.txt 2415
> /asterisk/trunk/lib/python/asterisk/TestConfig.py 2415
> /asterisk/trunk/lib/python/asterisk/version.py 2415
> /asterisk/trunk/runtests.py 2415
>
> Diff: https://reviewboard.asterisk.org/r/1454/diff
>
>
> Testing
> -------
>
> Tested included unit tests.
>
>
> Thanks,
>
> Matthew
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20111013/df995771/attachment-0001.htm>
More information about the asterisk-dev
mailing list