[mapserver-dev] Motion: move autotests into main mapserver repo

[Tom Kralidis]

+1.  Excellent improvement.

..Tom

On Wed, Feb 24, 2016 at 1:10 PM, thomas bonfort
<thomas.bonfort at gmail.com> wrote:
> Hi,
>
> We initially decided to separate our autotests into a distinct repository,
> mainly in order to be able to manage commit rights differently on the tests
> vs. the actual code. With hindsight, this was not an optimal solution as it
> creates a burden when updating/creating/accepting tests.
>
> After discussion with Even and Stephan, we would like to motion to move the
> autotests into a subdirectory of the main mapserver repository.
>
> Pros:
> - Tests are always in sync with the code they refer to
> - Adding tests along with a bugfix or feature is an atomic operation and
> does not require operating on two distinct commits on two distinct
> repositories
> - Updating tests on older branches will automatically be merged into the
> newer branches in the same way happening today for code.
>
> Cons:
> - The history of the tests will be lost in the main mapserver repo. The
> exisiting autotest repo will be kept read-only to be able to access this
> history should this rare need arise.
> - The initial checkout of the mapserver repo will be heavier as the tests
> need to be downloaded. This does not concern our release tarballs as the
> tests would not be included there.
>
> I would like to act quickly on this while we are still in sprint mode and
> have the time to iron out any issues.
>
> I'll start with my +1,
>
> Thomas
>
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev