use major version (4.*, 5.*) as tag for bugs

[kiranos]

look at issue #592

The fix was merged but I thought about it and its not always that the bug is in both versions.

its was not present in oc5 but existed in 4.* branch, to easier filter these it might be as simple as using tag for each branch and then its easier to find these bugs in the big list.

It might be good to add tags for mysql/sqlite, apache2/nginx etc to easier filter bugs and find replicas etc. Just a quick thought.

[BernhardPosselt]

good point. Theres no label for 5.0 yet though

[eMerzh]

yeah maybe we can reuse the v5.0.0alpha1 ...
i'm also interrested in a "postgresql" tag that can filter all issues related to postgres (not all those that have the word postgres in it)...

[tanghus]

👍 to all above :)

[eMerzh]

i've created a new V5.X label..... what do you think about removing all 4.5.[1,2,3,4,5,6] and set them to 4.5.x ?
and moving 5alpha to 5.x ?

[kiranos]

That would be great imo,

what about:

67 app:files
3 app:files_deleted
25 app:files_external
2 app:files_versions
2 app:search
14 app:user_ldap

Shouldnt these be moved to the apps repo? or I might be missing something, just the naming suggest it should be in the apps repo.

[VicDeo]

@kiranos the answer is https://github.com/owncloud/apps/blob/master/MAINTAINERS.md#other-repos

[bartv2]

I added the tags for the DB's

[kiranos]

great and as eMerzh wrote: i've created a new V5.X label..... what do you think about removing all 4.5.[1,2,3,4,5,6] and set them to 4.5.x ? and moving 5alpha to 5.x ?

I absolutely agree with removing all these 4.5.[1,2,3,4,5,6] variants, If the bug is not present ie fixed in the latest stable branch of said supported version that is 4.5.* it should be closed as fixed in master so there is really no need but supporting the latest version of each bransh?

[jancborchardt]

Tags are long added, closing this hence.