Ubuntu
dovecot package

  1. Bug #56057
  2. Comment #9

Comment 9 for bug 56057

Revision history for this message
Carlos Ribeiro (carribeiro) wrote : Re: [Bug 56057] Re: Dovecot complains about missing /etc/inetd.conf is missed during install

On 6/18/07, Soren Hansen <email address hidden> wrote:
> On Mon, Jun 18, 2007 at 12:29:49PM -0000, Carlos Ribeiro wrote:
> > Just a comment. In this case, can the bug be closed even if it was
> > reported in a LTS version (Dapper?). I thought LTS meant that bugs
> > *would be fixed*.
>
> It's important to remember, that in many cases, a bugfix is not merely a
> 1 that should have been a 0 something as simple as that. Often, to fix a
> bug, you need to rewrite anything between a few lines of code to several
> hundred lines of code. In doing so, it's likely that new bugs will be
> introduced. For that reason, a bug needs to be very significant to
> warrant an update in a released version of Ubuntu, as it may break
> things for other people which would be even worse.
>
> For that reason, we have a very strict policy when it comes to letting
> *anything* new come into a released version, especially an LTS one. You
> can read all about it here: https://wiki.ubuntu.com/StableReleaseUpdates
>
> In short, bugs are generally closed when they're fixed in the current
> development release. If you feel a bug is important enough to be fixed
> in previously releases of Ubuntu, you can post a comment to that effect,
> or you open a release task as explained in the wiki page I linked to
> above.

Ok, thanks for the clarification. As I said, it was just a comment on
my part, so please don't take me wrong.

So forgive me as I'm not a Launchpad Guru, I'm only a casual user...
Is it possible to mark bugs as closed for a release but still opened
or with a different status (ex: "Wont Fix" or "Workaround exists") for
previous releases? That would be useful not only for this particular
case but for any similar issue that affect a LTS release. Another idea
would be to document issues like this in the "Release Notes" for
Dapper - but I'm not sure if it would be worth the effort.

Thanks for the prompt answer and best regards.

--
Carlos Ribeiro
Consultoria em Projetos
blog: http://rascunhosrotos.blogspot.com
blog: http://pythonnotes.blogspot.com
mail: <email address hidden>
mail: <email address hidden>