Groundhog day in 7.8 repo ?

[Mnyb]

The nightly build process seems to run smoothly for once , so new builds are churned out now and then .

But what is it building ? As far as I can see for weeks/months on ends it building 1337855496 all over ?

Is it that absolutely nothing has been developed in weeks/months ? Git does not provide non programers with any good insights ? It is a bit fractured and hard to follow.

And why does it build when nothing is changed ? It gives the impression of activity when there is none ?

If out if ideas, fix a bug or two . If we accept that Most of bugzilla is dupes bogus or misplaced support cases to a factor 10/1
You would still have 100's of real issues.

The number of bugs is a bit misleading it includes fixed and invalid and duplicate bugs ,we don't have 17900 unfixed bugs then LMS would be classified as electronic warfare .

[erland]

The nightly build process seems to run smoothly for once , so new builds are churned out now and then .

But what is it building ? As far as I can see for weeks/months on ends it building 1337855496 all over ?

Is it that absolutely nothing has been developed in weeks/months ? Git does not provide non programers with any good insights ? It is a bit fractured and hard to follow.

I'm fairly sure you are already aware of this, but just in case, the commit history can be found here:
- For 7.8: https://github.com/Logitech/slimserver/commits/7.8
- For 7.7.x: https://github.com/Logitech/slimserver/commits/7.7

Except for some translation corrections there haven't been any public changes since May 10'th or something similar.
Likely either because people have been on vacation (we know Michael have) or because they are working on some new service or new hardware which they aren't ready to expose to the public repository yet, my personal guess would be that it's a combination of both. A big reason to switch to a git repository could have been that working on private branches in svn was probably a bit frustrating so it was a good idea to do the switch before starting work on new stuff.

And why does it build when nothing is changed ? It gives the impression of activity when there is none ?

There have been translation changes, but if builds are generated also on the dates where no changes has been done at all, it's likely caused by some bug in the build system, I'm sure they will eventually correct that.

If out if ideas, fix a bug or two . If we accept that Most of bugzilla is dupes bogus or misplaced support cases to a factor 10/1
You would still have 100's of real issues.

The number of bugs is a bit misleading it includes fixed and invalid and duplicate bugs ,we don't have 17900 unfixed bugs then LMS would be classified as electronic warfare .

I'm pretty sure nobody is running out of ideas, they are just working on something which can't be exposed to the public at the current stage.

Of course, I know nothing more than you about any of this, so the above are just guesses.
Based on all indications during last months I think it's more likely that they are working on new products/services than shutting down Squeezebox development as some people seems to think. Maybe we are about to get Rdio or Google Music support or maybe Squeezebox Boom HD, Squeezebox Air (as in Airplay) or Squeezebox Controller HD (tablet) is about to be released ;-)

[erland]

The number of bugs is a bit misleading it includes fixed and invalid and duplicate bugs ,we don't have 17900 unfixed bugs then LMS would be classified as electronic warfare .

I wonder if it would help them if we somehow listed duplicates and invalid bugs so someone with the right permissions can go through and close them ?

For invalid bugs or bugs that have already been solved but not closed, just listing them should be enough, then someone can go through the list can close them all.

For duplicates it's probably a good idea to add a comment in the bug report and maybe also provide a list of duplicates found so someone can go through and close all duplicates.