search

owncloud / smashbox-testing

Smashbox testing running on DroneCI
MIT License
1 stars 3 forks source link

Test most recent server release with development master branch of client #12

Closed mrow4a closed 5 years ago

mrow4a commented 5 years ago

@DeepDiver1975 @patrickjahns @tboerger

tboerger commented 5 years ago

The same argument as before, fine to test against branches, but not against fixed releases as failing tests can't get fixed.

mrow4a commented 5 years ago

@tboerger @patrickjahns it tests with client MASTER branch, which changes every day.. If client MASTER branch failed with 10.2 what do you do? Leave it be? Future client version won't be supporting 10.2?

tboerger commented 5 years ago

If the server got an issue it's not really fixable...

mrow4a commented 5 years ago

It is, correct bug in client master branch. @guruz can you try helping explain here? Would that make sense for you?

tboerger commented 5 years ago

And why are the stable10 and master branches not enough???

mrow4a commented 5 years ago

@tboerger stable10 is future version to be released... Why are we testing server with released client versions? E.g. server master with client 2.4?

Following that logic, we should not test released client versions every day.

tboerger commented 5 years ago

We are always testing with branches, not tags. That's the difference. Branches can always receive a fix, tags are fixed without any option to provide a fix.

Slowly I'm really out of all this smashbox stuff because it's boring to discuss this over and over again.

mrow4a commented 5 years ago

@tboerger master branch can receive a fix

tboerger commented 5 years ago

Only on client side.