Ubuntu Dev Summit Lays Out Plans For Hardy Heron 261
Opurt writes "On the first day of the Ubuntu Developer Summit in Boston this week, a roundtable session focused on the vision for the upcoming Hardy Heron Ubuntu release. Unlike Gutsy Gibbon, which brought a handful of experimental features along with some new functionality, the focus with Heron will be on robustness as it will be supported on the desktop for 3 years. 'The Compiz window manager, which adds sophisticated visual effects to the Ubuntu user interface, will be a big target for usability improvements. Keyboard bindings and session management were noted as two areas where Compiz still needs some work.' PolicyKit and Tracker will also be significantly tweaked, while Heron is also likely to see a complete visual refresh."
more details (Score:5, Informative)
Re:How about fixing things... (Score:4, Informative)
Yes, the workaround is to either download/install Eclipse manually or run Ant from the command-line, but it is annoying to see a basic feature still broken for weeks when it worked perfectly fine before.
Re:Looking at the release schedule (Score:3, Informative)
Yeah, and their current permissions tab on the folder/file properties dialog which was introduced in 2.18 (I think), made the whole dialog a whole lot taller. It's pretty ugly.
This is a good idea, in fact I'd be happy if instead of saying
Try VirtualBox, it'll blow you away
Re:can we just use numbers, please. (Score:5, Informative)
To make it clearer, development has just started on Hardy Heron, or what is likely to be known as 8.04. To start development the Ubuntu devs create repositories named after the codename (e.g. Hardy). If they used 8.04 and the deadline was missed and the release was actually 8.06 they wouldn't easily be able to change the repositories and other stuff.
The names are just code names, after release the number is the identifier that is used by Ubuntu (see if you can see 'Gutsy' on the Ubuntu.com front page, it's not there) its just usually the the code-names stick it peoples' minds.
So to sum up, the code names are there for a perfectly logical reason, and the animal thing is just a consistent naming theme that was chosen.
Re:How about fixing things... (Score:4, Informative)
Gutsy broke my vmware. Not expected and from what I hear there's no vmware in gutsy still. We who have technical know-how can still fix it, but it does seem that the QA-dept slipped a bit on Gutsy.
Kubuntu too? (Score:2, Informative)
(Please, no flame wars on Gnome v. KDE - it's just my preference and you have yours.)
Hmm, I should go try their forums too...
Re:Ubuntu To Do List (Score:5, Informative)
Re:Ubuntu To Do List (Score:2, Informative)
OS X's file system is no "cleaner" than Ubuntu's. Furthermore, OS X fails to conform to standard UNIX file system conventions.
Oh, and that attitude of yours is what I consider to be the *PRIMARY* thing that's wrong with Linux. But I guess it will be hard to fix as well...
That attitude of yours is what I consider to be the *PRIMARY* thing that's wrong with OS X.
In fact, there are many aspects of OS X that positively suck. You named some of them. Linux may need to imitate some aspects of Windows that suck simply because of the predominance of Windows in the market, but OS X's market share is so insignificant that the only features of OS X that are worth adopting in Linux are the ones that demonstrably are better than what Linux already has. File system organization, installers, and GUI designers are not among those.
Re:Ubuntu To Do List (Score:2, Informative)
I have a
One of my housemates built a linux system that relied on loopback fs images, mounted and combined with unionfs. He had basic packages that would be loaded into the unionfs, and the file trees merged. Then, the only files on the only rw branch of the union were config files he had changed, and his home directory. It was an absolutely fascinating system, and there were scripts for hot-loading new packages, with some restrictions on unloading due to the nature of unionfs (which he had hacked the kernel to get this functionality). When he started talking about creating a package manager, the discussion really ended with us saying he had just changed where the abstraction level of standard package managers was and the only real advantage was that altered files were in a separate filesystem, and easily sorted through. All the other advantages of the system are the same as in, for example, debian. You don't need to touch any files, or know where they'll be, to install OO.o, you just install the package, and everything is interleaved into your filesystem for you.
Naively creating a
Re:How about fixing things... (Score:4, Informative)
In the meantime, you just have to compile your own modules. It's very simple--it's a matter of running vmware-config.pl every time you upgrade the kernel, which will automatically take care of everything for you as long as you have build-essential installed.
As annoying as this is (and I find it mildly annoying, at least), it is the price of using a proprietary solution like VMware instead of similar Free solutions (like QEMU or VirtualBox).
Re:Maybe it's time Ubuntu got a icon (Score:3, Informative)
Re:Ubuntu To Do List (Score:4, Informative)