3

Sometimes, there are issues that affects one or many nightlies, and that are carried over since a stable release, or even before it.

For example, I'm currently running a CM13 nightly build, and have a Wi-Fi issue that's present since the first CM13 nightly, and which affected even the one stable build that was rolled out some months ago.

Given that the issue never changed, and so it doesn't depend on a specific nightly, which policy should be applied? Should such a question be flagged? Closed? Would it be legitimate to ask it?

2
  • 5
    Mentioning clearly in the question that the problem is a legacy issue carried over from stable versions and not a specific behaviour of only nightly builds ought to prevent a) flagging / closure b) Make it legitimate. My 2C. +1
    – beeshyams
    Sep 2, 2016 at 13:35
  • 1
    @beeshyams Would you care to post it as an answer, so I can accept it?
    – Grimoire
    Oct 22, 2016 at 6:37

1 Answer 1

Reset to default
2

As requested by OP:

Mentioning clearly in the question ( possibly prefacing so that knee jerk closure flags are not triggered) with a text on lines of

This question pertains to a problem that is a legacy issue carried over from stable versions and not a specific behaviour of nightly builds

This ought to prevent:

  • Flagging / closure of the question being a nightly related

  • Make it legitimate.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .