Skip to content
This repository has been archived by the owner on May 27, 2020. It is now read-only.

merge inn platform changes #7

Merged
merged 36 commits into from
Feb 9, 2016
Merged

merge inn platform changes #7

merged 36 commits into from
Feb 9, 2016

Conversation

andrerom
Copy link
Contributor

@andrerom andrerom commented Feb 3, 2016

merge in changes from platform as a first step towards doing a 1.1 release.

update: as agreed below this repo is as part of the merge adjusted to be closer to upstream.

andrerom and others added 28 commits January 12, 2016 12:18
Added missing behatbundle behat.yml to behat.yml.dist
Applies the ezpublish -> app rename to ezrouter.
Fixed internal server / ezrouter.php
Improve EZP-25369: Remove configuration from installers
https://jira.ez.no/browse/EZP-25383

This commit covers:
- Apache conf
- script

Todo: Nginx, Clustering, doc update
EZP-25383: Change web server conf to be able to generate from bash
Small update to directory permissions to align with Sf 2.8
Conflicts:
	composer.json
Bumped repository-forms requirements due to UGC (routing) addition.
@andrerom
Copy link
Contributor Author

andrerom commented Feb 4, 2016

@SylvainGuittard / @bdunogier POV on if this repo should be in close sync with ezplatform, or use stable packages as is the case?

@bdunogier
Copy link
Member

Both are valid. The merge of what happens in ezsystems/ezplatform@master will have to be manual anyway.

TL;DR:

  • demo must be tagged when master is tagged, within a small enough time (1 week ?)
  • demo master should follow ezplatform@master. Doing so will make point above easier.

In terms of actual demo of the product, it would be better if ezplatform-demo@master gave at all times a good view of where ezplatform is on the bleeding edge. If there are tags, they are what people will get anyway when installing. If you install ezplatform-demo@master, you will get the latest versions of the packages. Unless we have updated requirements in ezplatform@master, the latest version of ezsystems packages will be downloaded anyway.

@SylvainGuittard
Copy link
Contributor

Thanks @andrerom for the PR!
I think ezplatform-demo should be as close as possible to ezplatform.

+1

@andrerom
Copy link
Contributor Author

andrerom commented Feb 5, 2016

ok, will update this next week when 1.1.0 is out.

Bertrand Dunogier added 2 commits February 5, 2016 17:34
@bdunogier
Copy link
Member

It is out, you can go ahead. Note that there is a commit in the unstable
version that must be reverted (the one that sets the aliases).

Le ven. 5 févr. 2016 17:08, André R. notifications@github.com a écrit :

ok, will update this next week when 1.1.0 is out.


Reply to this email directly or view it on GitHub
#7 (comment)
.

@andrerom andrerom changed the title 1.1 update merge inn platform changes Feb 8, 2016
@andrerom
Copy link
Contributor Author

andrerom commented Feb 8, 2016

PR updated, as agreed I instead merge in changes from master, and then releases can be done as second step. (so yes, branch name is miss leading)

@bdunogier
Copy link
Member

branch name is miss leading

I knew about miss france or miss norway, not miss leading 👼

+1

@andrerom
Copy link
Contributor Author

andrerom commented Feb 9, 2016

I knew about miss france or miss norway, not miss leading 👼

she won over miss losing 🙆‍♀️

andrerom added a commit that referenced this pull request Feb 9, 2016
@andrerom andrerom merged commit 724f586 into master Feb 9, 2016
@andrerom andrerom deleted the 1.1_update branch February 9, 2016 14:04
@SylvainGuittard
Copy link
Contributor

Thanks @andrerom

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

Successfully merging this pull request may close these issues.

6 participants