All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Lenglet <rlenglet@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-core] About the versioning scheme in the repository
Date: Mon, 6 Mar 2006 15:59:57 +0900	[thread overview]
Message-ID: <200603061559.57932.rlenglet@domain.hid> (raw)

Hi,

When is the version number changed in the config/version file?
Is that value the version 1) of the next release being prepared, 
or 2) of the last release?

This is a concern for packaging. I would like to make two series 
of Debian packages: xenomai, libxenomai, etc. for the official 
releases, and xenomai-svn, libxenomai-svn, etc. for periodical 
extracts from the svn repository after releases.
The problem is: what versions to give to the *-svn packages? For 
instance, the current value in config/version is 2.0.93.
The current xenomai-svn package would then have version 
2.0.93+svn20060306 (or something like that).

Using versioning scheme 1), the next xenomai package would have 
version 2.0.93. This is bad, because the xenomai-svn could not 
be replaced by the next xenomai package:
2.0.93 < 2.0.93+svn20060306.
Even if xenomai (official release package) is more recent.

Using versioning scheme 2) works, because the next xenomai 
package would have version 2.0.94 (or 2.1 or...), and hence 
would have priority over the older xenomai-svn packages.


So, could someone confirm that what is currently done is scheme 
2), i.e. the version in config/version is modified just before 
tagging the repository and releasing?

-- 
Romain LENGLET


             reply	other threads:[~2006-03-06  6:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-06  6:59 Romain Lenglet [this message]
2006-03-06  8:11 ` [Xenomai-core] About the versioning scheme in the repository Philippe Gerum
2006-03-06  8:20   ` Romain Lenglet
2006-03-06 12:13     ` Gilles Chanteperdrix

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=200603061559.57932.rlenglet@domain.hid \
    --to=rlenglet@domain.hid \
    --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.