From: Paul <paul_c@domain.hid>
To: rpm@xenomai.org
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] debian/rules update
Date: Tue, 13 Mar 2007 20:32:26 +0000 [thread overview]
Message-ID: <200703132032.26296.paul_c@domain.hid> (raw)
In-Reply-To: <1173803432.16997.71.camel@domain.hid>
Hi Philippe
On Tuesday 13 March 2007 16:30, Philippe Gerum wrote:
> > A question for the project admins: Do you have a Release Manager to
> > coordinate package releases ?
>
> I'm currently coordinating the Xenomai releases, with input from the
> sub-systems/architecture maintainers. I guess that by "package", you are
> referring to another division of the work, though.
By "package", I mean binaries in the form of *.deb and/or *.rpm - Whilst I'm
happy to build and host i386/x86 Debian packages, I'm concerned about
treading on someone's toes without a discussion about revision numbers and
general policy about "official" releases. For example, the packages I've
built to date have used 2.3.50 even although a tarball of that version hasn't
been released.. That could well cause confusion for users and yourself if
bugs are reported. There is also a minor problem with keeping the
debian/changelog in sync.
One possible answer is for me to rebuild my repository from scratch and
append the SVN revision number to revision number so that we end up with
2.3.50-1~r2289 - This would allow an official 2.3.50-1 release to override
the ~r2289 revision..
Regards, Paul.
next prev parent reply other threads:[~2007-03-13 20:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 17:56 [Xenomai-core] debian/rules update Paul
2007-03-13 16:30 ` Philippe Gerum
2007-03-13 20:32 ` Paul [this message]
2007-03-14 10:56 ` Philippe Gerum
2007-03-14 10:59 ` Gilles Chanteperdrix
2007-03-14 11:14 ` Philippe Gerum
2007-03-14 16:48 ` Paul
2007-03-15 22:48 ` Philippe Gerum
2007-03-14 16:48 ` Paul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200703132032.26296.paul_c@domain.hid \
--to=paul_c@domain.hid \
--cc=rpm@xenomai.org \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.