[lm-sensors] Call for 2.10.1

[lm-sensors] Call for 2.10.1

[Jean Delvare]

Hi all,

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

Phil, will you continue taking care of the release? Our
doc/developers/checklist probably needs some adjustements to reflect
our move to SVN, amongst others.

Thanks,
-- 
Jean Delvare

[lm-sensors] Call for 2.10.1

[Tomislav Parčina]

In article <20060819105454.c6c438ed.khali at linux-fr.org>, khali at linux-fr.org says...
> 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. 

I vote for this one!



--
Tomislav Par?ina
Lama Computers Split
Stinice 12, 21000 Split
Tel.: +385(21)495148
Mob.: +385(91)1212148
SIP: tomo at pbx.lama.hr
e-mail: tparcina#lama.hr
http://www.lama.hr

[lm-sensors] Call for 2.10.1

[Hans de Goede]

Tomislav Par?ina wrote:
> In article <20060819105454.c6c438ed.khali at linux-fr.org>, khali at linux-fr.org says...
>> 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. 
> 
> I vote for this one!
> 

I missed the original post (to many mails, so trigger happy delete
finger) as already described I'm working on an abituguru2 driver for a
new much different version of the abituguru2. I would like to merge the
userspace support for this (and only the userspace) before 2.10.1 if
there is some time for this, so 1 questions:
1) is it ok to merge userspace support for a not yet released kernel
   driver?
2) how much time do I have before 2.10.1 ?

Regards,

Hans

[lm-sensors] Call for 2.10.1

[Tomislav Parčina]

> -----Original Message-----
> From: Hans de Goede [mailto:j.w.r.degoede at hhs.nl] 
> Sent: 21. kolovoz 2006 8:22
> To: Tomislav Par?ina
> Cc: lm-sensors at lm-sensors.org
> Subject: Re: [lm-sensors] Call for 2.10.1
> 
> I missed the original post (to many mails, so trigger happy delete
> finger) as already described I'm working on an abituguru2 
> driver for a new much different version of the abituguru2. I 
> would like to merge the userspace support for this (and only 
> the userspace) before 2.10.1 if there is some time for this, 
> so 1 questions:
> 1) is it ok to merge userspace support for a not yet released kernel
>    driver?
> 2) how much time do I have before 2.10.1 ?

Hi Hans!

Here is original post.

Bye.

****

Hi all,

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

Phil, will you continue taking care of the release? Our
doc/developers/checklist probably needs some adjustements to reflect
our move to SVN, amongst others.

Thanks,
-- 
Jean Delvare

[lm-sensors] Call for 2.10.1

[Jean Delvare]

> > -----Original Message-----
> > From: Hans de Goede [mailto:j.w.r.degoede at hhs.nl] 
> > Sent: 21. kolovoz 2006 8:22
> > To: Tomislav Par?ina
> > Cc: lm-sensors at lm-sensors.org
> > Subject: Re: [lm-sensors] Call for 2.10.1
> > 
> > I missed the original post (to many mails, so trigger happy delete
> > finger) as already described I'm working on an abituguru2 
> > driver for a new much different version of the abituguru2. I 
> > would like to merge the userspace support for this (and only 
> > the userspace) before 2.10.1 if there is some time for this, 
> > so 1 questions:
> > 1) is it ok to merge userspace support for a not yet released kernel
> >    driver?
> > 2) how much time do I have before 2.10.1 ?
> 
> Hi Hans!
> 
> Here is original post.

I'd like to remind both of you that we have a mailing list archive here:
http://lists.lm-sensors.org/pipermail/lm-sensors/

Thanks,
-- 
Jean Delvare

[lm-sensors] Call for 2.10.1

[Jean Delvare]

Hans,

> I missed the original post (to many mails, so trigger happy delete
> finger) as already described I'm working on an abituguru2 driver for a
> new much different version of the abituguru2. I would like to merge the
> userspace support for this (and only the userspace) before 2.10.1 if
> there is some time for this, so 1 questions:
> 1) is it ok to merge userspace support for a not yet released kernel
>    driver?

Yes it is, as long as you are reasonably certain that the driver's
interface won't change by the time it is merged.

> 2) how much time do I have before 2.10.1 ?

SVN freeze is scheduled for September 5th.

-- 
Jean Delvare

[lm-sensors] Call for 2.10.1

[Tomislav Parčina]

> -----Original Message-----
> From: Jean Delvare [mailto:khali at linux-fr.org] 
> Sent: 21. kolovoz 2006 19:00
> To: Tomislav Par?ina
> Cc: Hans de Goede; lm-sensors at lm-sensors.org
> Subject: Re: [lm-sensors] Call for 2.10.1
> 
> I'd like to remind both of you that we have a mailing list 
> archive here:
> http://lists.lm-sensors.org/pipermail/lm-sensors/

Hi Jean!

Thank you for reminding me.


Tomislav

[lm-sensors] Call for 2.10.1

[Jean Delvare]

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

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
> 
> Phil, will you continue taking care of the release? Our
> doc/developers/checklist probably needs some adjustements to reflect
> our move to SVN, amongst others.

Phil, you didn't answer to my question?

Thanks,
-- 
Jean Delvare

[lm-sensors] Call for 2.10.1

[Juerg Haefliger]

> > 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.

The current version of libsensors works fine with the new vt1211
driver. All it needs is a sligthly modified sensors.conf (and of
course an update to the 2.4 driver).

...juerg

[lm-sensors] Call for 2.10.1

[Philip Edelbrock]

On Sep 10, 2006, at 12:33 PM, Jean Delvare wrote:


>>
>> Phil, will you continue taking care of the release? Our
>> doc/developers/checklist probably needs some adjustements to reflect
>> our move to SVN, amongst others.
>
> Phil, you didn't answer to my question?
>

Hi Jean, yes I can.


Phil

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2439 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060910/abd11506/attachment.bin 

[lm-sensors] Call for 2.10.1

[Jean Delvare]

Hi Juerg,

> > > 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.
> 
> The current version of libsensors works fine with the new vt1211
> driver. All it needs is a sligthly modified sensors.conf (and of
> course an update to the 2.4 driver).

Good, thanks for testing and reporting. We can (and should) update both
right after the release.

-- 
Jean Delvare

[lm-sensors] Call for 2.10.1

[Jean Delvare]

Hi Phil,

> > Phil, will you continue taking care of the release? Our
> > doc/developers/checklist probably needs some adjustements to reflect
> > our move to SVN, amongst others.
> 
> Hi Jean, yes I can.

Great. The estimated release date is now Sunday, September 24th (or
anytime after that, depending on your own availability.)

Thanks,
-- 
Jean Delvare

[lm-sensors] Call for 2.10.1

[Jean Delvare]

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

[lm-sensors] Call for 2.10.1

[Juerg Haefliger]

Hi Jean,

I started working on the patch a couple of days ago and realized that
the current sensors does have some issues with the new 2.6 driver.
Since the temp mapping changed, the 'old' single alarms sysfs node now
has some bits swapped. So alaram reporting is broken.

...juerg


On 9/20/06, Jean Delvare <khali at linux-fr.org> wrote:
> Hi Juerg,
>
> > > > 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.
> >
> > The current version of libsensors works fine with the new vt1211
> > driver. All it needs is a sligthly modified sensors.conf (and of
> > course an update to the 2.4 driver).
>
> Good, thanks for testing and reporting. We can (and should) update both
> right after the release.
>
> --
> Jean Delvare
>

[lm-sensors] Call for 2.10.1

[Jean Delvare]

Hi Juerg,

> I started working on the patch a couple of days ago and realized that
> the current sensors does have some issues with the new 2.6 driver.
> Since the temp mapping changed, the 'old' single alarms sysfs node now
> has some bits swapped. So alaram reporting is broken.

Oops, good catch. This basically means that we must have the same order
for the 2.4 and the 2.6 driver, at the very least.

Will you have the time to provide a patch "fixing" the 2.4 driver by
the end of the week?

(One more reason to keep adding individual alarm bits to all drivers...)

Thanks,
-- 
Jean Delvare

[lm-sensors] Call for 2.10.1

[Philip Edelbrock]

On Sep 20, 2006, at 1:43 AM, Jean Delvare wrote:

> Hi Phil,
>
>>> Phil, will you continue taking care of the release? Our
>>> doc/developers/checklist probably needs some adjustements to reflect
>>> our move to SVN, amongst others.
>>
>> Hi Jean, yes I can.
>
> Great. The estimated release date is now Sunday, September 24th (or
> anytime after that, depending on your own availability.)

OK, sounds good.


Phil

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2439 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060920/0ff6df88/attachment.bin 

[lm-sensors] Call for 2.10.1

[Juerg Haefliger]

Hi Jean,

> Will you have the time to provide a patch "fixing" the 2.4 driver by
> the end of the week?

I believe so yes, but it won't be well tested (other than running
sensors and making sure the output under 2.6 and 2.4 match).

...juerg

[lm-sensors] Call for 2.10.1

[Jean Delvare]

Juerg,

> > Will you have the time to provide a patch "fixing" the 2.4 driver by
> > the end of the week?
> 
> I believe so yes, but it won't be well tested (other than running
> sensors and making sure the output under 2.6 and 2.4 match).

Should be good enough. At least it can't be worse than shipping a
version of libsensors/sensors with alarm bits which don't match the 2.6
driver channels - that could really confuse the users.

Thanks,
-- 
Jean Delvare

[lm-sensors] Call for 2.10.1

[Jean Delvare]

Hi Phil,

> > Phil, will you continue taking care of the release? Our
> > doc/developers/checklist probably needs some adjustements to reflect
> > our move to SVN, amongst others.
> 
> Hi Jean, yes I can.

We've got the green light, you can now release 2.10.1 as your schedule
allows :)

Both i2c and lm_sensors need to be released. You'll need to bump the
version of libsensors to 3.1.1.

As said above, please update doc/developers/checklist to reflect the
changes as you discover them. If there's any problem with the new
setup, please let Axel Thimm (and me) now, and we'll try to assist.

Thanks,
-- 
Jean Delvare

[lm-sensors] Call for 2.10.1

[Philip Edelbrock]

On Sep 24, 2006, at 1:29 PM, Jean Delvare wrote:

> Hi Phil,
>
>>> Phil, will you continue taking care of the release? Our
>>> doc/developers/checklist probably needs some adjustements to reflect
>>> our move to SVN, amongst others.
>>
>> Hi Jean, yes I can.
>
> We've got the green light, you can now release 2.10.1 as your schedule
> allows :)
>
> Both i2c and lm_sensors need to be released. You'll need to bump the
> version of libsensors to 3.1.1.
>
> As said above, please update doc/developers/checklist to reflect the
> changes as you discover them. If there's any problem with the new
> setup, please let Axel Thimm (and me) now, and we'll try to assist.


OK, great!


Phil

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2439 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060924/07925ed4/attachment.bin 

[lm-sensors] Call for 2.10.1

[Jean Delvare]

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

[lm-sensors] Call for 2.10.1

[Aurelien Jarno]

Jean Delvare a ?crit :
  > 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.

Thanks for your work everybody!

FYI there is a SVN commit file in the tarball of version 2.10.1:
W: lm-sensors source: svn-commit-file-in-source doc/svn-commit.tmp

Not a big problem it can be left there, but maybe that could be avoided 
for future releases.

Bye,
Aurelien

-- 
   .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
  : :' :  Debian developer           | Electrical Engineer
  `. `'   aurel32 at debian.org         | aurelien at aurel32.net
    `-    people.debian.org/~aurel32 | www.aurel32.net

[lm-sensors] Call for 2.10.1

[Philip Edelbrock]

On Sep 25, 2006, at 3:35 PM, Aurelien Jarno wrote:

> Jean Delvare a ?crit :
>> 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.
>
> Thanks for your work everybody!
>
> FYI there is a SVN commit file in the tarball of version 2.10.1:
> W: lm-sensors source: svn-commit-file-in-source doc/svn-commit.tmp
>
> Not a big problem it can be left there, but maybe that could be  
> avoided
> for future releases.

Oh, right, that's my bad.  I think it created that file the first  
time I tried to commit and it failed because I didn't have  
permissions.  There's nothing sensitive in that file and at least  
it's sort of hidden in doc/.  :'/  Thanks for noticing that.


Phil

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2439 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060925/2f9f0021/attachment.bin