[Dune] suggestion for testing

[Andreas Dedner]

 > Managing patches is actually the job of a version control system.  The
 > usual way of dealing with this problem is to have a testing branch
 > where all dubious patches go, people or test suites test this branch,
 > and patches that are found to be working fine are merged back to the
 > trunk.
I agree, but do you have a suggestion of how
this can be done without too much fuss?
Would this require a development branch in which
changes are committed and then they are merged
into the trunk after some testing. What would be
a good way of doing this?
Having a directory of the form
   dune.org/patches/today/patch*
would perhaps not be perfect but would be easy
to get working right a way. We could
then still discuss a more sophisticated
approach if the other one turns out to be
insufficient.
Andreas
approach



Sven Marnach wrote:
> Hi!
> 
> Oliver Sander schrieb am Mo, 19. Mai 2008, um 11:33:46 +0200:
>> The suggestion of more tests is always welcome.  I just
>> don't think sending patches around by email is a good
>> idea.  IMHO we need as many tests on as many platforms
>> as we can get, but we need them automatically, so no emails
>> get lost, and at a centralized place.
> 
> Managing patches is actually the job of a version control system.  The
> usual way of dealing with this problem is to have a testing branch
> where all dubious patches go, people or test suites test this branch,
> and patches that are found to be working fine are merged back to the
> trunk.  Unfortunately, merging doesn't work very well in svn, but I
> still think this is a much better solution than dealing with patches
> manually.
> 
> Greetings,
>     Sven
> 
> _______________________________________________
> Dune mailing list
> Dune at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune