Bug 46442 - Call1.I.Mute not considered stable
Summary: Call1.I.Mute not considered stable
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-spec (show other bugs)
Version: git master
Hardware: Other All
: medium normal
Assignee: Simon McVittie
QA Contact: Telepathy bugs list
URL:
Whiteboard: Call
Keywords: patch
Depends on:
Blocks:
 
Reported: 2012-02-22 05:06 UTC by Simon McVittie
Modified: 2019-12-03 20:25 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
Call.I.Mute: change <tp:added> version back to saying it's a draft (1.14 KB, patch)
2012-02-22 05:06 UTC, Simon McVittie 		Details | Splinter Review
Call: don't require the draft Mute interface (1.01 KB, patch)
2012-02-22 05:07 UTC, Simon McVittie 		Details | Splinter Review
View All

Description Simon McVittie 2012-02-22 05:06:49 UTC 
Created attachment 57454 [details] [review]
Call.I.Mute: change <tp:added> version back to saying  it's a draft

Mute was the only Call1 interface we didn't undraft in 0.25.2, but I was
too enthusiastic with the <tp:added/>.
Comment 1 Simon McVittie 2012-02-22 05:07:12 UTC 
Created attachment 57455 [details] [review]
Call: don't require the draft Mute interface

This doesn't make sense. Mute isn't final yet.
Comment 2 Simon McVittie 2013-11-04 17:00:02 UTC 
Are there any working implementations of this, or should we get rid of it?

(I'm vaguely trying to start Telepathy 1.0 without any draft interfaces, because that seems ridiculous: if they were actually stable API in disguise, we should undraft them, or if they were never stable, we should drop them.)
Comment 3 GitLab Migration User 2019-12-03 20:25:53 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-spec/issues/131.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.