-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This all depends on the definition of fix released - mine tends to be "in the ubuntu archive", which includes anything between when it is ACCEPTED (and hits gutsy-changes), and is actually published, and in the archive.
We (who are not archive admins) can't actually push the bugs any further than this - we have to wait for soyuz, etc, to sort itself out. So for all intents and purposes, i'd say that this should be marked Fix Released, yes. Also, the bug closing by changelog comes in somewhere - i think when the package itself is accepted - where it is automatically marked as fix released. Hobbsee GabrielGrant wrote: > Sarah: That's true, but it I thought a bug isn't supposed to be marked > as "Fix Released" until the fix is, in fact, available. Is that not the > intended distinction between the "Fix Committed" and "Fix Released" > statuses? > > Thanks, > -Gabriel > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHAH9P7/o1b30rzoURAqKkAKCENz99ViYdwHlmSjEMr31wGYSg5gCeKEX2 5WGCpMVzz14vYNxcUaBtpP4= =Fb90 -----END PGP SIGNATURE----- -- ABI changed without a corresponding soname change https://bugs.launchpad.net/bugs/117732 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug contact for ekiga in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
