>>>>> "Anthony" == Anthony Towns <aj@azure.humbug.org.au> writes:
Anthony> So, rather than uploading to "stable unstable", you
Anthony> upload just to "stable", and the change automatically
Anthony> gets propogated to unstable (and/or testing), unless
Anthony> there's a newer version already there.
This sounds like a good idea. Except only the source code can be
transfered from stable to unstable (to prevent problems others are
debating), which will mean:
upload to stable == upload to stable + source only upload to unstable
So one way or the other source only uploads need to be fixed.
I haven't considered testing in the above, the actual equation might
look more like:
upload to stable == upload to stable
+ source only upload to testing
+ source only upload to unstable
...but I am not sure of auto-builders using testing, or if any are
even available. Building against unstable and putting the result
straight into testing could be bad, if libraries don't exist in
testing for instance. I guess this is an issue that needs further
discussion.
I guess the upload to unstable should be omitted if this is an earlier
version. Same with testing.
You could also argue that the initial upload should be source only
to. That way you wont encounter bugs dues to maintainers accidently
building using unstable libraries.
--
Brian May <[EMAIL PROTECTED]>
