Bug 68602 - make README say dbus-glib is deprecated, bring back NEWS
Summary: make README say dbus-glib is deprecated, bring back NEWS
Status: RESOLVED FIXED
Alias: None
Product: dbus
Classification: Unclassified
Component: GLib (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Simon McVittie
QA Contact:
URL:
Whiteboard:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2013-08-27 11:25 UTC by Simon McVittie
Modified: 2013-10-21 11:26 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:

Attachments
README: replace with a deprecation warning (2.00 KB, patch)
2013-08-27 11:25 UTC, Simon McVittie 		Details | Splinter Review
Bring back NEWS (13.22 KB, patch)
2013-08-27 11:26 UTC, Simon McVittie 		Details | Splinter Review
Update HACKING for current status (2.17 KB, patch)
2013-08-27 11:26 UTC, Simon McVittie 		Details | Splinter Review
View All

Description Simon McVittie 2013-08-27 11:25:23 UTC 
In practice I've done most dbus-glib releases in recent years, and I find it easier to do release announcements if I've been maintaining a NEWS file as I go.

The README is also way out of date.
Comment 1 Simon McVittie 2013-08-27 11:25:54 UTC 
Created attachment 84698 [details] [review]
README: replace with a deprecation warning

Most of the README was really about libdbus anyway.
Comment 2 Simon McVittie 2013-08-27 11:26:11 UTC 
Created attachment 84699 [details] [review]
Bring back NEWS

I'm the only one who does dbus-glib releases these days, and I find it
easier to track changes as we go along than to construct a change
list during the release process.
Comment 3 Simon McVittie 2013-08-27 11:26:21 UTC 
Created attachment 84700 [details] [review]
Update HACKING for current status
Comment 4 Simon McVittie 2013-10-21 11:26:33 UTC 
Nobody reviewed this, but nobody said "no" either, so I'm going to assume that the person doing the work gets to write the documentation. Fixed in git for 0.102.

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.