-
Notifications
You must be signed in to change notification settings - Fork 28
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
market - 0.6.0 #574
Comments
Needs RC2/final rebuild due to #575 |
Also should all these app be included in the EE bundle now? https://github.com/owncloud/enterprise/issues/4020#issuecomment-648234614 There are some recently bundled apps like wopi |
@IljaN this has been raised to P2 as this will block the release |
Problem is that bundle api does not receive a version: https://marketplace.owncloud.com/api/v1/bundles.json. Market app should hide incompatible app versions client-side. |
@micbar I think this might be fixed if we release an enterprise_key app with max_version < 10.5 |
But we already have an enterprise-key app released with max version 10.x ... hmhhh |
@HanaGemela @davitol Is the installation of key app causing any errors? Possible Problem: There is code which tries to enable the enteprprise_key app after the bundle is downloaded. Possible 💥 if no enterprise_key app is present. |
@IljaN The enterprise_key app is deprecated. We must not try to install it. All remaining logic should be in core by now. |
I see but there are Problems ™️ : So the only viable solution from my pov is now:
|
Yes, good catch! We need to support both, 10.4.1 with enterprise-app and all the old enterprise logic, and new 10.5.x which should afaik work without enterprise-app. So second solution would be my suggestion. How much effort is that? |
IMHO I would choose also the second option, patching market app to honor version constraints of bundled apps. Not only for EE key app issue but also for example for adding WOPI to the 10.5 bundle as it was decided |
From: https://marketplace.owncloud.com/api/v1/bundles.json
|
Adding enterprise-app 0.2.0 to the current 10.5.0-complete bundle with max-version=10.4.1 and without <default_enable/> makes it appear in the diabled apps page as Having the app there but intended for not being used, is a bit confusing. But the red message is worse. An admin must assume something is wrong. |
The |
@pmaier1 IIRC, the decision on Friday was to include the enterprise_key app and work on the symptoms. No? |
If I'm not totally mistaken, the decision was to re-release it with a max-version=10.4.1 to prevent people on 10.5 from installing it from the Marketplace. Other than that 10.4.1 is the last version that includes it. @micbar Please enlighten us :) |
If it is possible, remove. it from the bundle for 10.5 @pmaier1 The problem is, we still need it for 10.4.1. These instances need to fetch it from the marketplace. So we said: if we cannot make the disctinction on the marketplace, we need to keep it in the bundle. |
Ok. I am not adding enterprise-key app to the bundle. we do a re-release to market place only with max-version=10.4 correct? |
@jnweiger Not sure If I understand enteprise_key is already in the bundle on marketplace? |
Enterprise key app is currently included in the marketplace EE bundle. @jnweiger won't include enterprise key app in the apps that are included in the complete tarball. |
|
@IljaN Testing market 0.6.0 RC2 included in ownCloud 10.5.1. RC4 Testing steps: 1 - Browse to the bundle section and install Enterprise bundle Current behavior A blank page appears in the browser and if you reload the browser, Internal server error is shown. Content of owncloud.log file below
|
I think the problem is within the objectstore app which tries to enable enterprise_key app which is not installed. From my POV a new release of objecstore app is required which remove the license-check from the app. @davitol Could you please repeat the test with disabled objectstore app to verify? |
staging enviroment needs to get the latest objectstore version 0.6.0. It is still with the old data |
@jnweiger @HanaGemela LGTM |
Reason
Product approval
info.xml
description and screenshotQA
development
toqa
Documentation
Marketing
Build
All actions to be done on the release branch from here:
info.xml
(no version suffix)info.xml
info.xml
Beta/RC
v${version}RC1
on release branchv${version}RC1
(seehandbook for how to build)
Final
v${version}
on release branchPublishing
#updates
channelPost-release
$version
master
branch withdescription "Closes #XYZ" with the release ticket number
The text was updated successfully, but these errors were encountered: