> Hence my question about karmic and jaunty; if it's packaged > for karmic then why not include it in jaunty repositories too.
When a release is marked as stable, it means that it will contain stable working no-important-error packages. The packages should run and their contents should be used without any problems. Karmic is still considered alpha and packages still keep coming in, whereas jaunty is considered stable and packages are updated only if they 're broken. Packages in karmic are going under testing, from alpha until beta, from there in release candidate and then a stable fully working release. In other words, shooting out each release can sometimes be dangerous. Maybe something won't work as expected, maybe it depends on other packages, maybe the package in karmic isn't perfect. If you include that package and then after a month or so, a user comes and says "Hi, my package isn't working", you need to check two packages, make another update, and so on and so forth. I believe that it is for the best that new packages go in new releases. Otherwise, I would suggest to consider a so-called "rolling release" operating system, such as Debian testing or Archlinux or Foresight Linux: http://en.wikipedia.org/wiki/Rolling_release Without being an expert, here are some interesting links for you to read: http://en.wikipedia.org/wiki/Software_release http://en.wikipedia.org/wiki/Release_engineering P.S. I'm neither a package maintainer (aka MOTU) nor Ubuntu/Canonical representative. :) -- [karmic] Please update hugin to 0.8.0 version https://bugs.launchpad.net/bugs/405234 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
