Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[3.2] Fix copyNode for case of file named 0 #1030

Merged
merged 1 commit into from Jan 22, 2018
Merged

[3.2] Fix copyNode for case of file named 0 #1030

merged 1 commit into from Jan 22, 2018

Conversation

phil-davis
Copy link
Contributor

Backport #1022 to 3.2 branch
Issue #1021

@staabm
Copy link
Member

staabm commented Jan 22, 2018

would you mind also backporting to 3.3?
(separate PR)

@phil-davis
Copy link
Contributor Author

3.3 backport also done.
It would be nice to have a 3.2.3 release (some other bits also recently added to 3.2 branch) since that makes it very easy to just get these bugfixes into ownCloud via existing composer, without waiting for a formal 3.3 release.

@staabm
Copy link
Member

staabm commented Jan 22, 2018

as we are new to the release process this might take some time. give us a few days/weeks to fiddle out how to do it properly ;)

@DeepDiver1975
Copy link
Member

@staabm shall we meet on irc for chatting about the release?

@staabm
Copy link
Member

staabm commented Jan 22, 2018

@DeepDiver1975 I guess we should but I have no spare time atm.

@staabm staabm merged commit 3e8249f into sabre-io:3.2 Jan 22, 2018
@DeepDiver1975
Copy link
Member

@DeepDiver1975 I guess we should but I have no spare time atm.

np - I'm in the sabredav irc channel on freenode - just stop by any time .... THX

@phil-davis phil-davis deleted the fix-copyNode-file-0-branch-3-2 branch January 22, 2018 10:43
@phil-davis
Copy link
Contributor Author

@staabm @DeepDiver1975 any progress on making a 3.2.3 etc release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants