Skip to content

merge roles into mainline develop for OMERO 5.4 series#5349

Merged
jburel merged 657 commits intodevelopfrom
roles
Jul 4, 2017
Merged

merge roles into mainline develop for OMERO 5.4 series#5349
jburel merged 657 commits intodevelopfrom
roles

Conversation

@mtbc
Copy link
Copy Markdown
Member

@mtbc mtbc commented Jun 28, 2017

What this PR does

Merges commits back from roles into develop.

Testing this PR

CI jobs should not show regressions.

pwalczysko and others added 30 commits May 10, 2017 15:15
Update Slack section to notify only when the success status is changed (rebased onto roles)
remove admin privileges bean from classes that no longer use it
cache OMERO sessions in Hibernate query cache
enforce protection of OriginalFile.repo property via database triggers
adjust Chgrp2, Chown2 for roles
more carefully prevent update/delete for user group
Tag version 5.3.2

Conflicts:
	components/blitz/src/ome/services/blitz/fire/Registry.java
	components/blitz/src/ome/services/blitz/repo/RepositoryDaoImpl.java
	components/tools/OmeroJava/test/integration/AbstractServerImportTest.java
	components/tools/OmeroJava/test/integration/ManagedRepositoryTest.java
@mtbc
Copy link
Copy Markdown
Member Author

mtbc commented Jun 28, 2017

I am happy to sign a milestone tag but how I do so usefully I forget. I can do the git tag -s v5.4.0-m1 -m ... locally but what next? Once this is merged I could fetch and sign develop's HEAD and push the tag to my fork.

@jburel
Copy link
Copy Markdown
Member

jburel commented Jun 28, 2017

you can also use scc tag-release -s release (no v)

@jburel
Copy link
Copy Markdown
Member

jburel commented Jun 28, 2017

when ready one of us can tag and push to origin
cc @sbesson @joshmoore

@mtbc
Copy link
Copy Markdown
Member Author

mtbc commented Jun 29, 2017

Not merged due to conflicts. Should we turn off the thing where non-breaking PRs also get included? I think that usually causes more trouble than it's worth.

@mtbc mtbc mentioned this pull request Jun 29, 2017
@mtbc
Copy link
Copy Markdown
Member Author

mtbc commented Jun 29, 2017

Now that @will-moore has kindly excluded #5347 the next obstacle is,

ERROR:  PostgreSQL database server version 9.3.15 is less than OMERO prerequisite 9.4.0

This does have the pleasing side-effect of testing @rleigh-codelibre's version number pretty-printing.

required to test on trout and eel before seabass is ready
temporarily allow PostgreSQL 9.3
@mtbc mtbc closed this Jun 29, 2017
@mtbc mtbc reopened this Jun 29, 2017
@mtbc
Copy link
Copy Markdown
Member Author

mtbc commented Jun 30, 2017

CI failures seem largely unrelated to this PR, "breaking" is broken. Leaving for either @jburel or @joshmoore to decide to remove --breaking once they are back and able to check in with @sbesson.

@mtbc mtbc mentioned this pull request Jul 3, 2017
4 tasks
@mtbc
Copy link
Copy Markdown
Member Author

mtbc commented Jul 3, 2017

After discussion, removed from breaking ready to test in mainline.

@jburel jburel added the develop label Jul 4, 2017
@mtbc
Copy link
Copy Markdown
Member Author

mtbc commented Jul 4, 2017

This breaks OMERO-DEV-merge-cpp but I expect we can live with that briefly. #5358 fixes the C++ build for me locally so I'll run that through devspace CI once Travis passes (especially as it adds to test_permissions.py) then switch the base branch to develop once this PR is in.

@jburel
Copy link
Copy Markdown
Member

jburel commented Jul 4, 2017

Merging this PR so we can move forward, I will tag when the PR fixing the c++ issue is in

@jburel jburel merged commit a430107 into develop Jul 4, 2017
@sbesson sbesson added this to the 5.4.0 milestone Oct 6, 2017
@joshmoore joshmoore deleted the roles branch November 21, 2017 12:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants