Bug#679041: transition: wireshark
On 06/28/2012 04:43 AM, BÃ¡lint RÃ©czey wrote:
2012/6/27 Adam D. Barratt <firstname.lastname@example.org>:
Can we schedule binNMUs for netexpect, or does it require any source
Eloy will upload the new netexpect package soon.
I uploaded to unstable new netexpect packages built against the new
Wireshark 1.8.0 packages yesterday as soon as I saw that Wireshark 1.8.0
had been accepted into unstable.
Note that 1.8.0~rc1-1 has been uploaded to the NEW queue weeks ago... 
In that case, I'm not entirely sure why the transition bug wasn't raised
"weeks ago"... nor what the logic is behind not having uploaded the
release version already, given that the upstream schedule claims it was
released a week ago.
In the past we managed the "transition" ourselves by quickly updating
netexpect after wireshark.
Since netexpect does not have too many users yet and netexpect is the
depending on wireshark it seemed to be a better solution over
involving the release team.
Should we always open a transition bug?
Last time, for the Wireshark 1.4 to 1.6 transition, we were not close to
a freeze, but BÃ¡lint and I coordinated the transition just like we did
this time. The end result was the same -- all packages and their
dependencies hitting unstable on the same day.