Bug tracker Editor category usage different?

Involved development of the OpenMW construction set.
User avatar
Jyby
Posts: 406
Joined: 10 Dec 2013, 04:16

Bug tracker Editor category usage different?

Post by Jyby » 20 Dec 2016, 16:46

I'm trying to find all features/bugs/tasks related to the editor in our bug tracker. I haven't determined the right search criteria, but what I noticed is inconsistent use of the category options (editor component vs editor framework). Can someone explain to me what the purpose of both are and if they provide any advantage over just an "editor" category?

In terms of a comprehensive search for editor related tickets, it would be wise to just have one category assigned to them.

Thanks
Macbook Air 2013 - 1.7GHz Intel i7 - 8 GB - 512 GB SSD - Intel HD 5000
Windows 10 PC - 4GHz Intel i7 - 16 GB - 512 GB SSD - EVGA GTX 1060 SSC

User avatar
Jyby
Posts: 406
Joined: 10 Dec 2013, 04:16

Re: Bug tracker Editor category usage different?

Post by Jyby » 20 Dec 2016, 17:14

Or, not sure how this would impact everyones workflow, could we create a new project OpenMW-CS and move all the editor tickets there? This would probably be the best solution IMO

Edit: An advantage would be not having to write "Editor" or "OpenMW-CS" in front of each ticket. The disadvantage would be compiling the change log to include "OpenMW-CS", unless someone personally scrubs it (like raevol?)
Macbook Air 2013 - 1.7GHz Intel i7 - 8 GB - 512 GB SSD - Intel HD 5000
Windows 10 PC - 4GHz Intel i7 - 16 GB - 512 GB SSD - EVGA GTX 1060 SSC

User avatar
Atahualpa
Posts: 791
Joined: 09 Feb 2016, 20:03

Re: Bug tracker Editor category usage different?

Post by Atahualpa » 20 Dec 2016, 21:01

Maybe not what you wanted to know but I've always asked myself why it it so difficult to put "OpenMW-CS:" in the issue's headline. I prefer to always add "OpenMW-CS" or "OpenMW" respectively -- if the issue is even more isolated, a hint to the affected part of the software may also help, e.g., "OpenMW-CS, script editor: ..." or "OpenMW, Control Settings: ..."

Currently, it's a huge challenge to work through the roadmap in order to produce a release commentary (or, in raevol's case, create a change log). And the headlines being ambiguous is only one part of the puzzle.

User avatar
Jyby
Posts: 406
Joined: 10 Dec 2013, 04:16

Re: Bug tracker Editor category usage different?

Post by Jyby » 20 Dec 2016, 21:06

I think creating a new project, "OpenMW-CS", would solve many issues. The big issue you pointed out is vague and non specific issues. Because we have shared resources between OpenMW and OpenMW-CS we need a way to address tickets concerning both products. For example there exists a bug related to handling deleted cell references that pertains to both OpenMW and OpenMW-CS.
Macbook Air 2013 - 1.7GHz Intel i7 - 8 GB - 512 GB SSD - Intel HD 5000
Windows 10 PC - 4GHz Intel i7 - 16 GB - 512 GB SSD - EVGA GTX 1060 SSC

User avatar
Zini
Posts: 5134
Joined: 06 Aug 2011, 15:16

Re: Bug tracker Editor category usage different?

Post by Zini » 21 Dec 2016, 10:07

In the early design stage of OpenMW there was a pretty clear distinction between the components (editing functions/panels for individual records/record-tables) and the framework in which these operate. Its not as clear cut now and the usefulness of the two categories has diminished. I would not object to having them merged into one. However that would have to be done on the backend/database/maintenance level (not sure if that is doable). Merging by individually changing every issue category is just a no go.

We decided to not have a separate project because there is a large amount of overlap between OpenMW and OpenMW-CS (obviously since both projects share quite a bit of code). Also, the plan is still to keep OpenMW and OpenMW-CS releases in sync (even if we have to make an exception for 1.0). Doing that with two different projects on the tracker just means more work.

User avatar
Jyby
Posts: 406
Joined: 10 Dec 2013, 04:16

Re: Bug tracker Editor category usage different?

Post by Jyby » 21 Dec 2016, 19:00

Who's the maintainer of the bug track? Could you set that up for us and I'll categorize any editor bugs not categorized I see.
Macbook Air 2013 - 1.7GHz Intel i7 - 8 GB - 512 GB SSD - Intel HD 5000
Windows 10 PC - 4GHz Intel i7 - 16 GB - 512 GB SSD - EVGA GTX 1060 SSC

User avatar
Zini
Posts: 5134
Joined: 06 Aug 2011, 15:16

Re: Bug tracker Editor category usage different?

Post by Zini » 22 Dec 2016, 14:53

lgromanowski does all our server stuff. However you should be able to change categories anyway.

User avatar
Jyby
Posts: 406
Joined: 10 Dec 2013, 04:16

Re: Bug tracker Editor category usage different?

Post by Jyby » 22 Dec 2016, 15:32

Ok I PM'd him with the migration request
Macbook Air 2013 - 1.7GHz Intel i7 - 8 GB - 512 GB SSD - Intel HD 5000
Windows 10 PC - 4GHz Intel i7 - 16 GB - 512 GB SSD - EVGA GTX 1060 SSC

User avatar
sjek
Posts: 407
Joined: 22 Nov 2014, 10:51

Re: Bug tracker Editor category usage different?

Post by sjek » 22 Dec 2016, 16:25

would vote for single interface. doing cross checking can be tedious at time. simpler solution would be making choise about openmw or openmw-cs mandatory.

on version checking and going trouhgt those all unlisted needs to be done anyway before 1.0
maybe placing redefined filters for issues but also maintaining those requires code knowledge and can be hassle but would work as indication
"life is crazy"
"craziness has beauty which only crazies understand" some movie clip in the head.
https://wiki.openmw.org/index.php?title=Testing

User avatar
lgromanowski
Site Admin
Posts: 1151
Joined: 05 Aug 2011, 22:21
Location: Wroclaw, Poland
Github profile: https://github.com/lgromanowski
Contact:

Re: Bug tracker Editor category usage different?

Post by lgromanowski » 22 Dec 2016, 23:43

I'll merge it at Monday

// Edit: 'Editor - component' and 'Editor - Framework' categories has been merged into one 'Editor'
best regards,
Lukasz

Post Reply

Who is online

Users browsing this forum: No registered users and 4 guests