From: "Timothy D. Witham" <wookie@osdl.org>
To: Linux Kernel ML <linux-kernel@vger.kernel.org>
Subject: Announcing Binary Compatibility/Testing
Date: Wed, 13 Oct 2004 15:16:53 -0700 [thread overview]
Message-ID: <1097705813.6077.52.camel@wookie-zd7> (raw)
Announcing Binary Compatibility/Testing
In talking to end users, distributions, OSS developers and
large scale ISV's one issue kept popping up. And that is
the fact that binaries keep breaking.
This is a real problem for large end users deploying Linux
in that they like to be able to run/roll forward the same version
of an application for 5 or so years. They can do this with their
legacy operating systems and we need to be able to do this
with Linux.
One of the big problems is that these ISV's release and test
on a cycle that is measured in calendar quarters and of course
the OSS cycle is measured in days. The idea is to move
testing of these binary applications upstream to match
the OSS development cycle. For this purpose I've started
a mailing list to discuss how to accomplish this. I've
got slides for anybody who is interested. (PDF.)
http://lists.osdl.org/mailman/listinfo/binary_sig
http://groups.osdl.org/sig (Follow binary testing for slides)
Let the flaming start. :-)
Tim
--
Timothy D. Witham - Chief Technology Officer - wookie@osdl.org
Open Source Development Lab Inc - A non-profit corporation
12725 SW Millikan Way - Suite 400 - Beaverton OR, 97005
(503)-626-2455 x11 (office) (503)-702-2871 (cell)
(503)-626-2436 (fax)
next reply other threads:[~2004-10-13 22:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 22:16 Timothy D. Witham [this message]
2004-10-13 22:38 ` Timothy D. Witham
2004-10-13 22:39 ` Jeff Garzik
2004-10-13 22:55 ` Timothy D. Witham
2004-10-13 23:24 ` Robert Love
2004-10-13 23:36 ` Timothy D. Witham
2004-10-14 18:32 ` Linus Torvalds
2004-10-14 21:57 ` Diego Calleja
2004-10-15 19:49 ` Matthias Urlichs
2004-10-17 21:44 ` Kurt Garloff
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=1097705813.6077.52.camel@wookie-zd7 \
--to=wookie@osdl.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®