Skip to content

Conversation

@nickvergessen
Copy link
Member

@nickvergessen nickvergessen commented Jul 16, 2019

Signed-off-by: Joas Schilling <[email protected]>
@MorrisJobke
Copy link
Member

info.xml needs a bump as well:

<nextcloud min-version="14" max-version="17"/>

@nickvergessen
Copy link
Member Author

which also means there has to be a new release available before 17, as well as 17 should be removed from the old stable branch and a new version be uploaded

@MorrisJobke
Copy link
Member

which also means there has to be a new release available before 17, as well as 17 should be removed from the old stable branch and a new version be uploaded

Correct.

@rullzer
Copy link
Member

rullzer commented Aug 15, 2019

@skjnldsv could you have a look?

Copy link
Member

@skjnldsv skjnldsv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code looks good :)

<bugs>https://github.com/nextcloud/preferred_providers</bugs>
<dependencies>
<nextcloud min-version="14" max-version="17"/>
<nextcloud min-version="17" max-version="18"/>
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claiming to be compatible with a version that is not even started yet? did you misunderstand the max-version? Or what's the reason behind it? if you have max-version="17" it will work with all 17 versions.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because I want to be able to work with it in 18?
As soon as we branch off on server, this will be compatible with 17 and 18.
This pr will not be merged until 17 is released and branched off :)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well but it defeats totally the porpuse of the field if you put it in the app store like this.
Same as before. the old version in the app store says it's compatible with 17, but it isnt 🤷

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, this release is a mistake :)
So I should just do min 17 max 17, right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, and after stable17 is branched of you increase it in master

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @nickvergessen :)

@rullzer
Copy link
Member

rullzer commented Aug 29, 2019

Then this is now good to go and ready for a release right?

@skjnldsv
Copy link
Member

SHould be yes :)

@skjnldsv skjnldsv force-pushed the bugfix/noid/notification-adjustments branch from 9b11d17 to 3f8c786 Compare January 27, 2020 15:15
@skjnldsv skjnldsv added the bug Something isn't working label Jan 27, 2020
@skjnldsv skjnldsv merged commit a70ddee into master Jan 27, 2020
@skjnldsv skjnldsv deleted the bugfix/noid/notification-adjustments branch January 27, 2020 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Log flooding: Simple signup is not fully compatible because it is using the old way to register

5 participants