[02:11] <micahg> jtaylor: sounds like a good idea, as tumbleweed said, get #ubuntu-release approval first
[02:58] <ScottK> micahg: It's up to the SRU team now.
[03:11] <micahg> ScottK: this was for Quantal :)
[03:11] <micahg> that is if I read backscroll correctly
[03:59] <ScottK> Oh.
[03:59] <ScottK> In that case, Ubuntu Archive would deal with removals.
[04:04] <micahg> ScottK: jtaylor: oh, sorry, I was referencing hdf5, not cpuid
[13:07] <jtaylor> why would it need release approval?
[13:08] <keffie_jayx> hello all, I have a question. With regards software that requires of a library released separate with its core features
[13:08] <tumbleweed> it doesn't need approval, but wouldn't hurt to let it be known that you'd like it synced before autosyncs start
[13:09] <keffie_jayx> does one package all that in one debian source package?
[13:09] <tumbleweed> keffie_jayx: a debian source package correlates to a tarball that an upstream releases
[13:10] <keffie_jayx> tumbleweed: ok that would make two then
[13:10] <keffie_jayx> and it would make one a build dependency and  dependecy of the other
[13:10] <keffie_jayx> good
[13:10] <keffie_jayx> thanks
[13:10] <tumbleweed> that works
[13:11] <keffie_jayx> I was confused since sometimes i seee only one dsc generation multiple binary packages
[13:11] <tumbleweed> that's pretty common
[13:12] <tumbleweed> especially for libraries. there'll be a separate -dev package, and possibly a -tools / -bin package, possibly a -doc, etc.
[13:18] <keffie_jayx> thanks tumbleweed
[18:30] <micahg> jtaylor: uploads before the release opens should be done with release team coordination ;)