All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Call for 2.10.7
Date: Mon, 23 Jun 2008 17:46:24 +0000	[thread overview]
Message-ID: <485FE170.2090304@hhs.nl> (raw)
In-Reply-To: <20080623132019.549ae84e@hyperion.delvare>

Jean Delvare wrote:
> On Mon, 23 Jun 2008 13:20:19 +0200, Jean Delvare wrote:
>> Hi all,
>>
>> Due to a compatibility issue between lm-sensors 2.10.6 and the upcoming
>> kernel 2.6.26 when option THERMAL is enabled, we have to release
>> lm-sensors 2.10.7 soon.
>>
>> There aren't that many changes as this is a legacy branch, nothing
>> worth mentioning here I think. See CHANGES in SVN trunk for the details.
>>
>> Proposed schedule:
>> * June 29th: SVN freeze
>> * June 30th - July 6th: testing
>> * July 7th: release
>>
>> Let me know if there is any problem with this.
> 
> Thinking about it some more, it would probably be better if lm-sensors
> 2.10.7 was released before kernel 2.6.26. And kernel 2.6.26 could be
> released soon, as we're at RC7 already. So maybe the following schedule
> would be better:
> 
> * June 25th: SVN freeze
> * June 26th-30th: testing
> * July 1st: release
> 
> This is admittedly tight but OTOH there's little activity on this
> legacy branch so I do not expect much problems (and I doubt a looser
> schedule would help find more bugs anyway.)
> 

+1

Regards,

Hans

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2008-06-23 17:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 11:20 [lm-sensors] Call for 2.10.7 Jean Delvare
2008-06-23 15:50 ` Jean Delvare
2008-06-23 17:46 ` Hans de Goede [this message]
2008-06-24  3:23 ` Philip Edelbrock
2008-07-01 16:47 ` Jean Delvare
2008-07-01 17:05 ` Philip Edelbrock
2008-07-01 19:11 ` Philip Edelbrock
2008-07-02 18:41 ` Jean Delvare

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=485FE170.2090304@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --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.