Björn Stenberg <[EMAIL PROTECTED]> writes: > During the release effort, a number of patches were submitted to the > project but were delayed until post-3.0. This is pretty normal. Now > that 3.0 is out the door and the users have a stable version to work > with, these new patches go in and a new unstable version 3.1 is > released.
Then it is the maintainers responsibility not to make pakages of the unstable version before he had maked sure that the stable version is ready for inclusion in testing. -- Peter Makholm | I have no caps-lock but I must scream... [EMAIL PROTECTED] | -- Greg http://hacking.dk |
