Debian Testing is in freeze to become Debian Stable, does PureOS follow?
Open, Needs TriagePublic

Description

This issue was created to keep T366 clean.

Debian is freezing Buster so we need to address syncing in packages from Debian Unstable (and/or Experimental) for L5 development. Is there a way to use the tools we have to do this?

I generally find that it is easier to handle issues when framed by describing the "issue" (i.e. the thing broken or missing) as the topic - rather than an open-ended question.

Does it perhaps make sense to change topic of this issue to "PureOS is too unstable when tracking Debian testing"?

Whoops, sorry: I totally misread this issue: Clearly not that PureOS is too unstable.

Does it perhaps make sense with topic "PureOS is too stable during Debian freeze"?

How can something be "too stable" or "too unstable"? Isn't it kind of like saying you're too pregnant? Either your pregnant, or you're not.

If foobar v5.0.1 is stable and foobar v6.0beta2 is unstable, then what is foobar v4.2? And what is foobar v6.0+git20190304?

I'd say stability is a sliding scale, so instead of the arguably binary "was the egg fertilized?" more like the more vague "is it an embryo?"

jonas.smedegaard closed this task as "Resolved".Thu, Apr 4, 8:28 AM
jonas.smedegaard claimed this task.

This issue has a question as its title. Is the issue then "Resolved" when the question is answered? And should we tag it "Invalid" if multiple conflicting answers emerge?

Seems this is framed not as an issue (where we need to address a thing to complete) but instead as a helpdesk (where we need to address someone - you - needing an answer).

Please consider framing this issue as an issue.

jonas.smedegaard reopened this task as "Open".Thu, Apr 4, 9:13 AM

Whoops, didn't mean to close this (just wanted to look for the exact terms used in there...)

Add Comment