All of lore.kernel.org
 help / color / mirror / Atom feed
From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Call for 2.10.1
Date: Mon, 25 Sep 2006 21:31:33 +0000	[thread overview]
Message-ID: <20060925233133.0e05663e.khali@linux-fr.org> (raw)
In-Reply-To: <20060819105454.c6c438ed.khali@linux-fr.org>

Hi all,

Quoting myself:
> I think it's about time to release lm_sensors 2.10.1. The list of
> changes since our last release, 2.10.0, is getting quite long. The most
> important changes are probably:
> * Many fixes in libsensors
> * decode-dimms.pl completely reworked
> * Many cleanups and improvements to sensors-detect
> And of course support added for many new chips.
> 
> As far as I am concerned, the only thing I'd like to merge before this
> upcoming release is the set of changes needed to make the Linux 2.6
> vt1211 driver work properly. If you think of other things that need to
> be done before the release, please speak up.
> 
> Proposed schedule:
> September 5th: SVN freeze
> September 6th-20th: Testing
> September 21st: Release

Almost in time... The 2.10.1 release is there, ready for download!
Thanks to Philip Edelbrock for taking care of this release, and to both
Axel Thimm and Philip for the migration to Axel's server. Not
everything's perfect yet, but we appear to be able to address most
problems quickly so I have good hope things will only improve over time.

I would like the next release to happen "soon". There were more than 7
months between 2.10.0 and 2.10.1, which was too much IMHO. I know that
the move to a the server didn't help in that respect, but now that this
is done we should be able to release more often. As long as libsensors
needs specific code for every new chip we add support for in the Linux
2.6 kernel tree, we should try to match the kernel releases to make
sure people with the latest released kernel can use the latest released
lm_sensors and expect things to just work. This means a release every 3
months or so, which sounds reasonable to me.

Of course, once we have a completely chip-independent libsensors, we
can again leave more time between releases. But we're not there yet.

I'll do the Freshmeat announcement tomorrow.

-- 
Jean Delvare


  parent reply	other threads:[~2006-09-25 21:31 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
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 [this message]
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=20060925233133.0e05663e.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.