Process for bugs that are not valid on newest release

Asked by Michael Hatcher

Hi to all,

I have recently started looking through the smaller bugs to contribute and have noticed that there are a fair number of them that are reporting issues at freya beta and freya final release and I am trying to find what the expected stance on these are. I usually test against the most recent release and if the issue is no longer present, assume that the bug would be marked as fixed and then closed but wanted to confirm to make sure that I am following the expected process.

Any information I can gain into the process with help so that I am not tying up resources of more experienced devs on here.

Thanks

Question information

Language:
English Edit question
Status:
Answered
For:
elementary OS Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Cassidy James Blaede (cassidyjames) said :
#1

Yes, if it is a bug that has been fixed in the latest release, Fix Released is the way to go. If it is a bug that technically isn't fixed but is not relevant to the latest release, you can probably mark it as Won't Fix. Just make sure to comment so anyone following the bug knows why the status changed!

Can you help with this problem?

Provide an answer of your own, or ask Michael Hatcher for more information if necessary.

To post a message you must log in.