chromium-browser version regressions

This forum is dedicated to packaging and translating :

On those activities rely the making of Mageia Linux Distribution.

Post all questions and information about packaging and translating : feedbacks, discussion about guidelines, packaging practices...

chromium-browser version regressions

Postby diensthunds » Apr 13th, '13, 07:33

This applies to the Mageia 3 release

While trouble shooting a bug with the sync server for chromium-browser I noticed that the beta, stable and unstable versions are not corelating with the numbering.

chromium-browser-beta is 26.0.1410.46
chromium-browser-stable is 26.0.1410.51
chromium-browser-unstable is 25.0.1354.0

the beta and the stable makes sense the .46 to the .51 increase but why does the unstable go down not a minor number but an entire major number? It's down from 26 to 25.
I thought that normally an unstable would be a higher build that hasn't been proven to be (relatively) bug free and operational on a daily basis, then once it's fixed it would be labeled stable and the next unstable would be yet another higher build number.
Am I off in thinking that the following would make sense?

beta 25.0.1354.0
stable 26.0.1410.46
unstable 26.0.1410.51

Or is there a particular reason why it's labeled as such? I see that the beta and the unstable are coming from the mga repo while the stable is from the tainted but shouldn't things hold the same (version to label wise) across the board?

What is it about the unstable version that makes it go into the tainted repo?
diensthunds
 
Posts: 3
Joined: Apr 23rd, '12, 03:15

Return to Packaging and translating for Mageia

Who is online

Users browsing this forum: No registered users and 1 guest

cron