From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Call for 2.10.1
Date: Wed, 20 Sep 2006 08:47:55 +0000 [thread overview]
Message-ID: <20060920104755.09f58b30.khali@linux-fr.org> (raw)
In-Reply-To: <20060819105454.c6c438ed.khali@linux-fr.org>
Quoting myself:
> > Proposed schedule:
> > September 5th: SVN freeze
>
> A few days late, but we're there. The SVN repository is now considered
> frozen. Only bugfixes and documentation updates are allowed until we
> release.
>
> > September 6th-20th: Testing
> > September 21st: Release
There's some sliding in the schedule, and the estimated release date is
now September 24th (next Sunday.) Everyone please give good testing to
the current SVN version by then. Areas which specifically need testing
are:
* Proper support of older kernels (both 2.4 and early 2.6)
* sensors-detect
* decode-dimms.pl
But really any kind of testing is welcome anyway.
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2006-09-20 8:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-19 8:54 [lm-sensors] Call for 2.10.1 Jean Delvare
2006-08-21 6:10 ` Tomislav Parčina
2006-08-21 6:21 ` Hans de Goede
2006-08-21 8:21 ` Tomislav Parčina
2006-08-21 17:00 ` Jean Delvare
2006-08-21 17:04 ` Jean Delvare
2006-08-22 6:34 ` Tomislav Parčina
2006-09-10 19:33 ` Jean Delvare
2006-09-10 20:32 ` Juerg Haefliger
2006-09-11 4:26 ` Philip Edelbrock
2006-09-20 8:40 ` Jean Delvare
2006-09-20 8:43 ` Jean Delvare
2006-09-20 8:47 ` Jean Delvare [this message]
2006-09-20 15:39 ` Juerg Haefliger
2006-09-20 16:30 ` Jean Delvare
2006-09-20 16:59 ` Philip Edelbrock
2006-09-20 17:42 ` Juerg Haefliger
2006-09-20 18:40 ` Jean Delvare
2006-09-24 20:29 ` Jean Delvare
2006-09-24 21:42 ` Philip Edelbrock
2006-09-25 21:31 ` Jean Delvare
2006-09-25 22:35 ` Aurelien Jarno
2006-09-25 22:59 ` Philip Edelbrock
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=20060920104755.09f58b30.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=lm-sensors@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 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.