Rockbox 3.0 Release Upgrade

[mreude]

I've believe I have upgraded Rockbox to the the latest release, but would like to know if there is any way to tell on my iPod. I am using Windows XP SP3 with an iPod 5th gen 30gb Video. I am also using the 1.0.7 release of the Rockbox Utility

Thanks.

[karashata]

The version info should have a 3.0 after the revision number and before the date (basically, r#-3.0-[date]).

[mreude]

Ok, right after I upgrade to the latest release 3.0 it says r#-3.0-[date], but once I've copied the "current build" to my iPod it returns to r#-[date]. Any insights?

[Llorean]

If you copy the current build to it, you aren't exactly using the release version any more are you? I mean you've just replaced it with the current build instead...

[mreude]

So, is the newest "current build" based on the version 3.0 release?

[karashata]

Not really, the newest "current" build is built off the latest SVN commit.  Release 3.0 is based off an older SVN revision (r15815 or somewhere close to there, I believe).

[mreude]

How will one know if the current build is related to the latest release version 3.0?

[karashata]

The current build is newer than the release and has a few more recently added features/fixes/etc. added.  It's only direct relation it that it still supports everything that version 3.0 supports.

[Llorean]

What do you mean "Related"?

3.0 was just a version. All newer versions are exactly that: Newer versions. Every version of Rockbox comes from the same code evolution. It's just a line.

Karashata's statement isn't entirely true, there's very strong relation in that "all the code used to make 3.0 later lead to all later versions".

[soap]

Not sure I follow the question.
The way things work is:
Every single change to Rockbox is offered to users as a "current build".
We're talking multiple versions of Rockbox every day.

To make the 3.0 release, Rockbox development was "frozen" for a few weeks, and no changes except bug repairs were made during said freeze.

Once the frozen version was at a point people were happy (enough) with the stability it was branded "3.0" and there will be no more changes.  (Changes which bring new features but also perhaps new bugs.)

A major bug repair will likely be "back ported" from the current version to the 3.0 version and be named "3.0.1" or some such, but outside that 3.0 today is what 3.0 will be next year.

So, if you want stability and super smart swift support, 3.0 is your dream.
If you want the latest and greatest and are willing to deal with a higher probability of bugs, "current builds" are in your future.

[mreude]

So, are all builds after the 3.0 release based from that release?

[saratoga]

So, are all builds after the 3.0 release based from that release?

More like 3.0 is based on a build from about a month ago, with minor changes.

[mreude]

Ok, so, is it better to use the 3.0 release version or the current build?

[soap]

So, if you want stability and super smart swift support, 3.0 is your dream.
If you want the latest and greatest and are willing to deal with a higher probability of bugs, "current builds" are in your future.

Mind you, Rockbox has a history of very few bugs which will interfere with your enjoyment.

[karashata]

You may also want the current builds if you've seen a feature added recently that you'd like, that isn't supported by the 3.0 release.  For example, MP3 processing on the PortalPlayer coprocessor, for the iPods, the Sansas, and the iriver H10s.