* [lm-sensors] Call for 3.3.1
@ 2011-07-03 12:14 Jean Delvare
2011-07-03 17:42 ` Guenter Roeck
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Jean Delvare @ 2011-07-03 12:14 UTC (permalink / raw)
To: lm-sensors
Hi all,
According to trac [1], we're running late on the release schedule.
There aren't many changes in the queue [2], but shipping an up-to-date
version of sensors-detect alone seems to warrant a maintenance release
every 3 or 4 months.
[1] http://www.lm-sensors.org/roadmap
[2] http://www.lm-sensors.org/browser/lm-sensors/trunk/CHANGES
We will also have to replace every reference to the Linux 2.6 kernel to
"2.6 or 3" or "2.6 or later". Volunteers welcome...
I propose the following schedule:
* July 13th: repository freeze
* July 14th-18th: testing and documentation updates
* July 19th: release
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [lm-sensors] Call for 3.3.1
2011-07-03 12:14 [lm-sensors] Call for 3.3.1 Jean Delvare
@ 2011-07-03 17:42 ` Guenter Roeck
2011-07-21 20:44 ` Jean Delvare
2011-07-22 2:58 ` Philip Edelbrock
2 siblings, 0 replies; 4+ messages in thread
From: Guenter Roeck @ 2011-07-03 17:42 UTC (permalink / raw)
To: lm-sensors
On Sun, Jul 03, 2011 at 08:14:26AM -0400, Jean Delvare wrote:
> Hi all,
>
> According to trac [1], we're running late on the release schedule.
> There aren't many changes in the queue [2], but shipping an up-to-date
> version of sensors-detect alone seems to warrant a maintenance release
> every 3 or 4 months.
>
> [1] http://www.lm-sensors.org/roadmap
> [2] http://www.lm-sensors.org/browser/lm-sensors/trunk/CHANGES
>
> We will also have to replace every reference to the Linux 2.6 kernel to
> "2.6 or 3" or "2.6 or later". Volunteers welcome...
>
> I propose the following schedule:
> * July 13th: repository freeze
> * July 14th-18th: testing and documentation updates
> * July 19th: release
>
Hi Jean,
there is an update for sensors-detect in your review queue, and I'll another one
for for a couple of National devices after that. Would be great if you could find
the time to review the pending patch. Alternatively, I could just go ahead and commit
the changes - just let me know.
I'll see if I find the time for the 2.6->3,0 changes. No promises, though.
Thanks,
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [lm-sensors] Call for 3.3.1
2011-07-03 12:14 [lm-sensors] Call for 3.3.1 Jean Delvare
2011-07-03 17:42 ` Guenter Roeck
@ 2011-07-21 20:44 ` Jean Delvare
2011-07-22 2:58 ` Philip Edelbrock
2 siblings, 0 replies; 4+ messages in thread
From: Jean Delvare @ 2011-07-21 20:44 UTC (permalink / raw)
To: lm-sensors
Hi Guenter, all,
On Sun, 3 Jul 2011 10:42:44 -0700, Guenter Roeck wrote:
> On Sun, Jul 03, 2011 at 08:14:26AM -0400, Jean Delvare wrote:
> > Hi all,
> >
> > According to trac [1], we're running late on the release schedule.
> > There aren't many changes in the queue [2], but shipping an up-to-date
> > version of sensors-detect alone seems to warrant a maintenance release
> > every 3 or 4 months.
> >
> > [1] http://www.lm-sensors.org/roadmap
> > [2] http://www.lm-sensors.org/browser/lm-sensors/trunk/CHANGES
> >
> > We will also have to replace every reference to the Linux 2.6 kernel to
> > "2.6 or 3" or "2.6 or later". Volunteers welcome...
> >
> > I propose the following schedule:
> > * July 13th: repository freeze
> > * July 14th-18th: testing and documentation updates
> > * July 19th: release
>
> there is an update for sensors-detect in your review queue, and I'll another one
> for for a couple of National devices after that. Would be great if you could find
> the time to review the pending patch. Alternatively, I could just go ahead and commit
> the changes - just let me know.
Processes meanwhile.
> I'll see if I find the time for the 2.6->3,0 changes. No promises, though.
I finally did it, it was easy, and committed and release lm-sensors
version 3.3.1. It's available for download now.
Philip, please copy the files to your mirror as your time permits. Thanks!
--
Jean Delvare
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [lm-sensors] Call for 3.3.1
2011-07-03 12:14 [lm-sensors] Call for 3.3.1 Jean Delvare
2011-07-03 17:42 ` Guenter Roeck
2011-07-21 20:44 ` Jean Delvare
@ 2011-07-22 2:58 ` Philip Edelbrock
2 siblings, 0 replies; 4+ messages in thread
From: Philip Edelbrock @ 2011-07-22 2:58 UTC (permalink / raw)
To: lm-sensors
[-- Attachment #1.1: Type: text/plain, Size: 539 bytes --]
On Jul 21, 2011, at 1:44 PM, Jean Delvare wrote:
> I finally did it, it was easy, and committed and release lm-sensors
> version 3.3.1. It's available for download now.
>
> Philip, please copy the files to your mirror as your time permits. Thanks!
Thanks, Jean.
I have it mirrored now. I updated the wiki to take the 'coming soon' out on the link, too.
Hope you and others on the list are doing well.
Phil
PHIL EDELBROCK + phil@studiogeologie.com + tel 541 753 4003 + G E O L O G I E + www.studiogeologie.com
[-- Attachment #1.2: Type: text/html, Size: 5323 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-07-22 2:58 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-07-03 12:14 [lm-sensors] Call for 3.3.1 Jean Delvare
2011-07-03 17:42 ` Guenter Roeck
2011-07-21 20:44 ` Jean Delvare
2011-07-22 2:58 ` Philip Edelbrock
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.