The weird thing is, the testing before the initial release was zero. It
didn't work with any JVM on any machine. But when the release is final,
it becomes very difficult to patch a package. You will need to get all
kinds of permissions and such.

I would say: 
 - less bureaucracy when patching packages after final release.
 - more bureaucracy when adding a package to a release before its final

And if it doesn't work at release time, do not include the package at
all. Maybe it'll be in time for the next ubuntu-release, but it missed
this one.

Sort of something like: it requires 10 people to say 'yeah, it works'
before it can even reach the final universe-repository. (before that it
should just be in proposed like a patch is after the final release)

Considering the fact that its one of those programs at least 20% of all
new users will install first (because they were also using it on
windows), it makes a really bad impression of Ubuntu. Would it not be in
the repositories, they would have downloaded it from the site, and it
would have worked. However, will they know that the repository version
is weird hacked up version? No, they won't. They won't try the upstream
version, they will give up. Perhaps on a Ubuntu as a whole.

-- 
Azureus does not start
https://launchpad.net/bugs/57875

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to