From: "Eric M. Ludlam" <eric@siege-engine.com>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: CEDET version
Date: Mon, 21 Jan 2013 23:06:28 -0500 [thread overview]
Message-ID: <50FE1044.1010307@siege-engine.com> (raw)
In-Reply-To: <0ca9s2ht87.fsf@fencepost.gnu.org>
On 01/21/2013 09:00 PM, Glenn Morris wrote:
> David Engster wrote:
>
>> Actually, it's more like a 1.2 since 1.1 was already released some time
>> ago, and the now bundled files are newer.
>>
>> It is a bit difficult since we bundle a subset of CEDET with Emacs, so
>> upstream versions cannot be really identical. Since we're now merging
>> more regularly, maybe we don't need upstream releases anymore and should
>> see it more as in incubator.
>>
>> In any case, I think calling this version "1.1.5" or "1.2" should be
>> fine, but I'd like to know what Eric thinks.
I'm ok with either of those version numbers. If official released
CEDETs are now whatever shows up in Emacs core, that would be fine with
me also. Wrapping up a release, and figuring out how to get it to
safely overlay in Emacs is a bit challenging.
> We can call it whatever version number you like. I think the only real
> issue is when using ELPA to install a newer version of CEDET than the
> version supplied with Emacs (but maybe this won't be happening?).
>
> There are various things that this affects; see M-x list-packages
> output. semantic, srecode, inversion, pulse, ede, etc. They all have
> different version numbers at present.
These used to all go out separately and were later merged into once
CEDET package. Is there a reason to version-merge them? To be honest,
updating all those version numbers each time we prep a release is a bit
of a pain, and they all install together. The cross-version-checking
isn't as useful a tool as it once was.
I do have some scripts I use to manage version numbers though. It could
be that whenever a merge occurs, we add running this script to the merge
recipe and that will help.
Eric
next prev parent reply other threads:[~2013-01-22 4:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-17 9:57 Emacs pretest 24.2.92 sindikat
2013-01-17 23:38 ` Glenn Morris
2013-01-18 1:59 ` Stephen J. Turnbull
2013-01-18 2:09 ` CEDET version [was Re: Emacs pretest 24.2.92] Glenn Morris
2013-01-21 2:20 ` CEDET version Glenn Morris
2013-01-21 19:13 ` David Engster
2013-01-22 2:00 ` Glenn Morris
2013-01-22 4:06 ` Eric M. Ludlam [this message]
2013-01-22 19:10 ` Glenn Morris
2013-01-22 22:51 ` Eric M. Ludlam
2013-01-23 7:38 ` David Engster
2013-01-23 13:17 ` Eric M. Ludlam
2013-01-23 20:39 ` David Engster
2013-01-31 0:04 ` Eric M. Ludlam
2013-01-31 20:08 ` David Engster
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=50FE1044.1010307@siege-engine.com \
--to=eric@siege-engine.com \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.