https://bugs.kde.org/show_bug.cgi?id=512748
--- Comment #17 from surcouf <[email protected]> --- (In reply to tnemeth from comment #15) > (In reply to surcouf from comment #14) > > >Thanks :) > > > I'll wait for the package to appear in Debian Testing ;) > > > > What is the logic behind the apparition of a package update in Debian > > testing? Does it come because a user triggers it? Or does it come after a > > given piece of time? Or another logic? > > Upstream makes a new version --> the debian developer in charge of the > package > creates the new package (at his/her own time appreciation) --> the > package is > pushed to "sid" (Unstable, "Still In Development") --> automatic analysis > tools are > used to check for package consistency --> after a week without reports > (some users > test packages in Unstable : those are the really dedicated ones) the > package is moved > to Testing where more timid users (like me) can test a system that is > (almost) up to date > with the state of the art. > > Every 2 years (something like that) Testing freezes progressively and > when all problems > are resolved Testing is moved to Stable. Then, about a week after, > Testing thaws and a > stream of ready Unstable packages flows into it. That was the case last > summer. > > Thomas. Thanks for the explanations. Regarding this specific bug, I presume it can be closed, since Thomas Baugart committed his fix into master and 5.2 branches, cannot it? -- You are receiving this mail because: You are watching all bug changes.
