On 7/24/07, Andrew Bartlett <[EMAIL PROTECTED]> wrote:
Keep testing and reporting issues, particularly on samba-technical and
in bugzilla.
We have a wide range of clients to keep working, so just checking all
sorts of combinations is a great help. It's not just windows:
- Samba 3.0 (latest)
- Samba 3.0 (older) - someone can remind me when we changed the join
code
- Mac OSX
Naturally, checking windows versions is also really helpful:
- Win2k SP0 (tricky kerberos issues make it an interesting test)
- win2k latest SP
- winXP SP0
- winXP SP1
- winXP SP2
- win2k3
- win2k3 SP1
- win2k3 R2 with SP2
This is a bit of a tangent, but I've been curious how the Samba team
does testing like this during development. Is it primarily done
manually? Has anyone tried setting up something like VMware to do
some automated testing? Were there any particular issues involved in
doing so?
Josh Kelley
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
