From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Call for 2.10.7
Date: Tue, 01 Jul 2008 16:47:48 +0000 [thread overview]
Message-ID: <20080701184748.3e789496@hyperion.delvare> (raw)
In-Reply-To: <20080623132019.549ae84e@hyperion.delvare>
On Mon, 23 Jun 2008 20:23:04 -0700, Philip Edelbrock wrote:
>
> On Jun 23, 2008, at 8:50 AM, Jean Delvare wrote:
>
> > 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.)
> >
> > Phil, would that be OK with you? I can do the release if you are busy
> > but you're still the one signing the 2.10.x packages.
>
> I should be just back from a trip then and be able to handle the
> release. I'll put it on my calendar.
OK, I'm done with testing, I think we are ready to release.
libsensors version needs to be bumped to 3.1.6.
i2c needs not be released (only one, minor change.)
Phil, please release as your schedule permits.
Thanks,
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2008-07-01 16:47 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
2008-06-24 3:23 ` Philip Edelbrock
2008-07-01 16:47 ` Jean Delvare [this message]
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=20080701184748.3e789496@hyperion.delvare \
--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.