Slashdot Mirror

← Back to Stories (view on slashdot.org)

Debian Update: Stretch Frozen, Bug-Squashing Parties Planned (phoronix.com)

Posted by EditorDavid on from the Debian-daily-news dept.

"Debian project leader Mehdi Dogguy has written a status update concerning the work going on for the first two months of 2017," reports Phoronix. An anonymous reader quotes their report: So far this year Debian 9.0 Stretch has entered its freeze, bug squashing parties are getting underway for Stretch, the DebConf Committee is now an official team within Debian, a broad Debian Project roadmap is in the early stages of talk, and more.
Bug-Squashing Parties have been scheduled this week in Germany and Brazil, with at least two more happening in May in Paris and Zurich, and for current Debian contributors, "Debian is willing to reimburse up to $100 (or equivalent in your local currency) for your travel and accommodation expenses for participating in Bug Squashing Parties..." writes Dogguy, adding "If there are no Bug Squashing Parties next to your city, can you organize one?"

3 of 55 comments (clear)

  1. Does it still work well without systemd? by gweihir · · Score: 1, Informative

    Debian 8 does. As long as that is the case, I do not care who wants to shoot themselves in the foot using that malware.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    1. Re:Does it still work well without systemd? by KiloByte · · Score: 3, Informative

      While Stretch still installs that malware by default, it actually works a bit better with a sane init than Jessie. Stretch also has a remarkable lack of regressions when compared to, for example, Wheezy->Jessie, so you can upgrade safely already.

      --
      The creatures outside looked from Alt-Right to Antifa; but already it was impossible to say which was which.
  2. Re:Debian bugs by Anonymous Coward · · Score: 2, Informative

    As in, bugs caused by the Debian team messing around with upstream software

    For the record:

    The OpenSSL patch was given the OK by the upstream OpenSSL developers at the time and the Debian maintainers trusted that.

    The xscreensaver upstream author inserted a low-grade malware time bomb in his code specifically to create a problem, just to be a dick with a plausibly reasonable complaint. In the ensuing uproar he clearly demonstrated himself to be someone I never want to be on a team with. He simply didn't get that "stability" in the Debian sense means well tested and well understood code, drawbacks and all. If you want the up to date channels use the Testing or Unstable branches and you will get new versions of things. It has been this way for about 20 years now so I guess people just assume others are aware of it. Compare that against the diplomacy and respectful to all parties way that the Debian maintainer eventually resolved the bug.

    Debian bills itself as a "stable" distro, but I always end up having more trouble with Debian

    My experience over most of the life of the distribution does not match yours.