Attachment 45385 Details for Bug 34870 – Mention dbus-specification.xml's separate versioning in HACKING

[patch] Mention dbus-specification.xml's separate versioning in HACKING

0004-Mention-dbus-specification.xml-s-separate-versioning.patch (text/plain), 1.39 KB, created by Simon McVittie on 2011-04-07 08:33:33 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Simon McVittie

Created: 2011-04-07 08:33:33 UTC

Size: 1.39 KB

patch

obsolete

>From f15c6d66ca73d3fbee77118b94f1a5617e3577a2 Mon Sep 17 00:00:00 2001
>From: Simon McVittie <simon.mcvittie@collabora.co.uk>
>Date: Thu, 7 Apr 2011 16:31:06 +0100
>Subject: [PATCH 4/4] Mention dbus-specification.xml's separate versioning in HACKING
>
>---
> HACKING |    7 ++++++-
> 1 files changed, 6 insertions(+), 1 deletions(-)
>
>diff --git a/HACKING b/HACKING
>index 7a5a792..64dc040 100644
>--- a/HACKING
>+++ b/HACKING
>@@ -154,6 +154,10 @@ To make a release of D-Bus, do the following:
> 
>  - update the file NEWS based on the git history
> 
>+ - verify that the version number of dbus-specification.xml is
>+   changed if it needs to be; if changes have been made, update the
>+   release date in that file
>+
>  - update the AUTHORS file with "make update-authors" if necessary
> 
>  - the version number should have major.minor.micro, even
>@@ -175,7 +179,8 @@ To make a release of D-Bus, do the following:
>  - bump the version number up in configure.ac (so the micro version is odd),
>    and commit it.  Make sure you do this *after* tagging the previous
>    release! The idea is that git has a newer version number
>-   than anything released.
>+   than anything released. Similarly, bump the version number of
>+   dbus-specification.xml and set the release date to "(not finalized)".
> 
>  - merge the branch you've released to the chronologically-later
>    branch (usually "master"). You'll probably have to fix a merge
>-- 
>1.7.4.1
>

Actions: View | Splinter Review

Attachments on bug 34870: 44235 | 45376 | 45377 | 45382 | 45384 | 45385

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.