Bug 6258 - First window in Windows Installer says 7.0a1
: First window in Windows Installer says 7.0a1
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Windows Installer
: 7.0
: PC Windows XP
: P2 normal (vote)
: ---
Assigned To: Michael Herger
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-11-30 15:03 UTC by Mickey Gee
Modified: 2009-09-08 09:29 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mickey Gee 2007-11-30 15:03:19 UTC
Using SqueezeCenter installer for windows dated November 30th it says version is SqueezeCenter 7.0a1. Probably should be 7.0.

Screenshot attached.
Comment 1 Michael Herger 2007-11-30 16:07:32 UTC
It's not been changed in any of the installers (and many other places, too).
Comment 2 Blackketter Dean 2007-12-17 12:15:46 UTC
We'll need to make sure that all the version numbers are updated before release.

Comment 3 Michael Herger 2007-12-18 00:06:26 UTC
Sure. When is this going to happen? Now or when we release?
Comment 4 Michael Herger 2007-12-19 09:08:50 UTC
Change 15472 - please test _all_ installers and readme/getting started documents and re-open if needed. Thanks!
Comment 5 Mark Miksis 2007-12-19 14:37:52 UTC
Michael,

I want to make sure I understand how this might affect the RPM.  AFAIK, all 6.x releases have 3 digit numbers (ie, 6.5.4).  Will that be the same for 7.x?  I had assumed that the first official release will be 7.0.0 and that at that point there will be a 7.0 branch (working toward a 7.0.1 release) and trunk will be working toward a 7.1.0 release.  Is that right?
Comment 6 Michael Herger 2007-12-19 15:02:06 UTC
We decided to call it 7.0, although there will very likely be a 7.0.1. Can't you use 7.0.0 internally (or just for the RPM)?
Comment 7 Mark Miksis 2007-12-19 15:20:58 UTC
It's probably OK (and less confusing) to use 7.0, especially if that's what the tarball is called.  I need to think about how this works when we have 3 different RPMs (trunk, branch and release).  Will 7.0 be branched prior to release as has been done in the past?  It's easy to mess this and break updates (where yum thinks a newer version is really older).  I want to make sure that "yum update" works properly, for example, from branch to release or from release to trunk.
Comment 8 Blackketter Dean 2007-12-19 17:46:12 UTC
Ah, I'm happy for it to be 7.0.0, I just thought that dropping that ending zero would be fine.

How about for the formatted cases where it matters (like the RPM) we use 7.0.0, and in all the human readable places use 7.0?

Either way, it's not a big deal to me.  


Comment 9 Mark Miksis 2007-12-20 09:27:09 UTC
The more I think about it, I don't think either way causes any RPM-specific problems other than the fact that some of the examples I posted for Matt will be different.  Actually, there might be some issues upgrading from my testing repo since I called it 7.0.0 - not sure.  Not a big deal though.

Independent of the RPM, I have to wonder whether a scheme that uses 7.0 in some places and 7.0.0 in others is a good idea.  I can imagine, after 7.0.1 is out, a lot of forum posts that take 2 or 3 follow-ups just to figure out *which* 7.0 the user has installed...
Comment 10 Michael Herger 2007-12-21 06:18:58 UTC
That's sorted out, isn't it? Can I close again?
Comment 11 Mickey Gee 2007-12-21 09:21:14 UTC
Looks fine on Windows installer! I won't close this until Fletch gives it the OK.
Comment 12 Mark Miksis 2007-12-21 10:03:01 UTC
No need to wait for me - as I said we can make the RPM and yum work either way.  But, note that Matt is still using 7.0.0 for the RPM.  It seems to me that a final decision hasn't really been made yet.  You might want to leave this open because if you guys decide to go with 7.0.0 then Michael's fix will need to be updated.
Comment 13 Michael Herger 2007-12-23 23:13:09 UTC
Thanks for the feedback.
Comment 14 Chris Owens 2008-03-07 09:04:28 UTC
This bug is being closed since it was resolved for a version which is now released!  Please download the new version of SqueezeCenter (formerly SlimServer) at http://www.slimdevices.com/su_downloads.html

If you are still seeing this bug, please re-open it and we will consider it for a future release.