Active Topics
-
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 17 hrs, 51 mins ago -
The N900 is now 15 years old! (6)
to Nokia N900 by Macros - 2 days, 14 hrs ago -
F(x)tec Pro1x (QWERTY) for sale (0)
to Buy & Sell by aln00000 - 3 days, 2 hrs ago - more...
| The Following 3 Users Say Thank You to For This Useful Post: | ||
|
2010-08-19
, 06:39
|
|
Banned |
Posts: 3,412 |
Thanked: 1,043 times |
Joined on Feb 2010
|
#32
|
Originally Posted by timoph
Yes it is a Linux project but the problem is Nokia will control the foundation merely by the fact of what they will alow to be open and not, that was my point and directed at Nokia not Qgil but he is a Nokian so i guess he falls in that bracket but not directly obvioulsy as he is only a small cog.
Please don't do this to yet another thread. I really don't see any reason to get offensive so please calm down. Also please read the text behind the link that qgil provided. If there's something in there that you don't understand or agree with please ask politely and you will be answered politely and this won't turn into a another flame war and abusing thread (that people with knowledge and expertise tend to stay away from).
FYI: MeeGo is not a Nokia project, it's a Linux Foundation project. Also it's not aimed to some specific device, it's a mobile OS for a wide range of devices.
 |
|
2010-08-19
, 07:03
|
|
Posts: 4,672 |
Thanked: 5,455 times |
Joined on Jul 2008
@ Springfield, MA, USA
|
#33
|
Originally Posted by abill_uk
Well, no. They can't control the source or foundation, but they can control how it appears on their own products. My fear is that they will repeat their history, Intel might lose interest and, in the end, MeeGo dies on the vine before it even gets a fair chance to show itself off. I really hope Nokia improves and learned from their past mistakes, but I'm still quite cynical about those chances.
Yes it is a Linux project but the problem is Nokia will control the foundation merely by the fact of what they will alow to be open and not, that was my point and directed at Nokia not Qgil but he is a Nokian so i guess he falls in that bracket but not directly obvioulsy as he is only a small cog.
|
|
2010-08-19
, 07:27
|
|
Posts: 1,418 |
Thanked: 1,541 times |
Joined on Feb 2008
|
#34
|
Originally Posted by buurmas
No, they will not.
THIS thread is looking ahead to MeeGo. Will things get better going forward?
|
|
2010-08-19
, 07:57
|
|
Posts: 2,802 |
Thanked: 4,491 times |
Joined on Nov 2007
|
#35
|
Originally Posted by qgil
Ok, that makes perfect sense for the netbook variant. When a new release arrives you just upgrade your computer (just as one does with distributions like Fedora or Ubuntu that have similar release cycles, BAU).
The MeeGo project makes a new release every 6 months. Each release is supported with full maintenance for a year and then for emergency fixes for a second year.
http://wiki.meego.com/Release_Engine...lease_Timeline
Will the same be possible Nokia MeeGo handheld devices? Ie, will someone buying the MeeGo-Harmattan device this fall be able to upgrade to the spring 2011, fall 2011 and so on releases as they come along? It's not the end of the world if that means going to "vanilla" MeeGo and losing the Nokia differentiation.
| The Following 2 Users Say Thank You to lma For This Useful Post: | ||
|
|
2010-08-19
, 07:57
|
|
Posts: 999 |
Thanked: 1,117 times |
Joined on Dec 2009
@ earth?
|
#36
|
I'm hoping we all being a bit paranoid and a bit cynical (which is understandable).
As far as I understand there will be an "official" Meego release every 6 months starting from October (e.g. Meego 1.1). In between official releases anyone can download, compile and package their own "developer" or "unstable" release - this release will not be official.
Something similar like a Linux kernel release, or Xorg and gnome platform for example.
I imagine that Nokia will time new hardware releases to coincide with official Meego releases - something like Debian, Ubuntu & gnome.
If you are technically-minded you keep a rolling-release cutting-edge version running on your device.
Otherwise you would wait for an official release then run it on your device.
Each release build on the previous while keeping compatibility.
The problem will be the closed-source drivers. If at some point a change in Meego is made (e.g. a new version of the kernel) which renders the closed-source driver incompatible.
(ATI deeming cards legacy and not supporting them in later versions of their closed-driver)
But as this is Nokia I would not expect too much common-sense.
As far as I understand there will be an "official" Meego release every 6 months starting from October (e.g. Meego 1.1). In between official releases anyone can download, compile and package their own "developer" or "unstable" release - this release will not be official.
Something similar like a Linux kernel release, or Xorg and gnome platform for example.
I imagine that Nokia will time new hardware releases to coincide with official Meego releases - something like Debian, Ubuntu & gnome.
If you are technically-minded you keep a rolling-release cutting-edge version running on your device.
Otherwise you would wait for an official release then run it on your device.
Each release build on the previous while keeping compatibility.
The problem will be the closed-source drivers. If at some point a change in Meego is made (e.g. a new version of the kernel) which renders the closed-source driver incompatible.
(ATI deeming cards legacy and not supporting them in later versions of their closed-driver)
But as this is Nokia I would not expect too much common-sense.
__________________
I like cake.
I like cake.
| The Following 3 Users Say Thank You to johnel For This Useful Post: | ||
 |
|
2010-08-19
, 08:30
|
|
Posts: 319 |
Thanked: 289 times |
Joined on Sep 2009
@ Lisboa, Portugal
|
#37
|
Originally Posted by gerbick
+1. This sums up everything I want to know.
So... could you commit to answering this question. Are you stating that each release means a new device, or will you allow 1.1 to be updated to 1.2 on the same machine and state it in terms that other vendors have stated in their upgrade paths?
I hate to use Apple as an example, but they've stood by their update pattern of 3 "major" revisions of their OS (ex. iOS 1.0 to 2.0 to 3.0) per device and all iterations therein are considered inclusive (ex. iOS 2.1, 2.2, 2.3.1 are "minor" revisions).
And how are the major revisions handled in MeeGo? Would 1.1 a major revision over 1.0, or would it be a minor revision (a dot increase)?
So to recap, what are the upgrade patterns for the upcoming MeeGo device, will it get support for that next 6 month iteration you've mentioned at least once, would it get a fully supported OS update to the next two iterations (1 year) or what?
Care to clarify what's known/unknown as it applies to each machine in terms of when it comes out and how many updates it will get; or are we looking at a single release, any updates we get for the OS are within those next six months and then looking forward to a new OS release (think: Maemo 5 to MeeGo and it will not be official, only community based support)?
Thanks in advance.
qgil?
|
|
2010-08-19
, 08:33
|
|
Posts: 724 |
Thanked: 1,255 times |
Joined on Nov 2007
@ Cambridge, UK
|
#38
|
@johnel
The drivers would need to be compiled with any new kernel release. This will hopefully be achieved with the autobuilder for those closed components. Nokia have the source for the closed blobs and have set up a system to continuously build the closed blobs and make them available for us to use.
When compilation breaks, hopefully these drivers can be fixed. The biggest problem will be API incompatible with new kernel versions and the closed components.
The drivers would need to be compiled with any new kernel release. This will hopefully be achieved with the autobuilder for those closed components. Nokia have the source for the closed blobs and have set up a system to continuously build the closed blobs and make them available for us to use.
When compilation breaks, hopefully these drivers can be fixed. The biggest problem will be API incompatible with new kernel versions and the closed components.
| The Following 5 Users Say Thank You to tswindell For This Useful Post: | ||
|
|
2010-08-19
, 08:33
|
|
Posts: 3,319 |
Thanked: 5,610 times |
Joined on Aug 2008
@ Finland
|
#39
|
Originally Posted by gerbick
What qgil said has nothing to do with this. Product support is one thing and MeeGo as a standalone project is another. He specifically didn’t speak about upgrades, but API compatibility. IIUC It’s pretty much the same situation as Android, Google won’t ship you a 2.2 image for a HTC Hero - that would have been HTC’s job, but then again Motorola did that for the Droid. MeeGo as such won’t (and can’t) guarantee what the future plans of the vendor will be (unless upgradeability actually becomes part of the MeeGo compliance program, which is unlikely).
So to recap, what are the upgrade patterns for the upcoming MeeGo device, will it get support for that next 6 month iteration you've mentioned at least once, would it get a fully supported OS update to the next two iterations (1 year) or what?
EDIT: And an important note about Apple. They are working by the rule of precedent - not to dismiss the track record, but those weren’t guaranteed upgrades, you assume 2 major upgrades because that was the practice during the last release, not because it has been announced previously (i.e. they announce on OS release what PREVIOUS devices will get it, not what FUTURE upgrades this device will get).
__________________
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
Blogging about mobile linux - The Penguin Moves!
Maintainer of PyQt (see introduction and docs), AppWatch, QuickBrownFox, etc
Last edited by attila77; 2010-08-19 at 08:41.
|
|
2010-08-19
, 08:42
|
|
Banned |
Posts: 3,412 |
Thanked: 1,043 times |
Joined on Feb 2010
|
#40
|
Originally Posted by tswindell
There you go it is still all about uncertainty and if's, why oh why can Nokia not do something right for us !?.
@johnel
The drivers would need to be compiled with any new kernel release. This will hopefully be achieved with the autobuilder for those closed components. Nokia have the source for the closed blobs and have set up a system to continuously build the closed blobs and make them available for us to use.
When compilation breaks, hopefully these drivers can be fixed. The biggest problem will be API incompatible with new kernel versions and the closed components.
Asking about the drivers will probably result in a non-answer, so let's ask about what is being touted the most - the openness of the platform and the direction(s) it could mean for each released device in terms of a MeeGo product.
I for one don't see a real problem with 1.1, 1.2, 1.3 and so forth to be loaded onto a device ad inifinitum - thus bringing us closer to a portable and updateable computer - but in this case, nobody knows for sure what Nokia has in store and what they think of their Linux Foundation connection. I'm running Ubuntu 10.04 on a machine that once ran Slackware 4.0.
That's an upgrade path I cannot argue against. Having that kind of flexibility on my MeeGo device would require Nokia to think in those same terms.
Instead of "hoping", I'm asking.