Release search_elastic 2.1.0

[ahherrera]

Reason

• Validate if there are elastic search servers configured before indexing the nodes pending updates.
• Add user and password authentication.

Product approval

• Verify transifex commits are in master: If a folder https://github.com/owncloud//tree/master/l10n exists, then https://drone.owncloud.com/owncloud/ should receive nightly '[tx] updated from transifex` ...
• Ping pmaier to check info.xml description and screenshot
• Get approval on translations from pmaier - send the date of the last tx commit from drone to Patrick

QA

• Create QA Milestone and set the description to $version
• Move tickets from milestone development to qa (testplan and tickets mentioned in release ticket)
• Create release branch with the format "release-$version"
• Create "$version Testplan" (QA templates or Enterprise) -> [QA] 2.1.0 Testplan #254
• copy new/reopened issues from the previous release ticket as 'Issues to review' below.
• check if Non-normal Release Process applies, and adapt this checklist.

Documentation XXX

• Changes in the docs needed? If so create issue in owncloud/docs-server. -> [QA] search_elastic 2.2.0 has a new admin UI docs-server#101

Marketing

• Ping @owncloud/marketing
• Update https://confluence.owncloud.com/display/PROD/Upcoming+Releases
• Request a screenshot if the app is new or changed fundamentally

Build

All actions to be done on the release branch from here:

• Bump version in info.xml (no version suffix)
• Bump "sonar.projectVersion=" in sonar-project.properties (no version suffix)
• Check php version dependency in info.xml
• Check minimum ownCloud version dependency in info.xml
• Change CHANGELOG.md 'Unreleased' to '$version' (today's date)

Beta/RC

• Ping product owner to create github tag for v${version}-rc1 on release branch (see https://confluence.owncloud.com/display/EN/Product+Owners+List)
• Build and sign RC tarball from github tag v${version}-rc1 (see handbook for how to build)
• Upload as Github release using changelog entries
• Test and document in testplan + manual explorative testing:
  • If this is an enterprise app: Enabling the app must start the grace period
  • If this is the initial release of an app: Check that the minimum version constraint resolves correctly
  • Add section "Changlog Testing" using github releases text or CHANGELOG.md from release branch
  • Do changelog tests
  • Do regression tests
  • smoke test with docker image owncloud/server:latest
  • => Final "Go" from QA (set 'QA-ready' label) => else do another RC after fixing issues in the "release-$version" branch

Final

• Check that no documentation issues are pending
• Rename last RC tarball to final
• Create github tag for final v${version} on release branch
• Upload as Github release using changelog entries

Publishing

• Upload tarball to marketplace (see handbook in confluence for details)
• Publish tarball for customers - old 10, old 10.0 and new portal (see handbook for details)
• Send mail to release-coordination with link to this ticket and to the changelog
• Copy email to rocket chat #updates channel

Post-release

• Add a new 'Unreleased' section in CHANGELOG.md (and also update links at the bottom!)
• Create PR to merge changes back to the master branch with description "Closes #XYZ" with the release ticket number
• Rename QA milestone to $version and close the milestone
• Update https://confluence.owncloud.com/display/PROD/Upcoming+Releases
• Ensure release template is up to date
• Ensure the testplan template (community or enterprise) is up to date
• Close the testplan issue

[mmattel]

Authentication is imho docs relevant as there are changes in the UI or config parameters. Can you please file a docs issue in docs-server and add some screenshots and a bit of description?

@EParzefall fyi

[jnweiger]

Issues opened while testing RC1

• ES7: The length of [file.content] field of [0] doc of [oc-ocu5gka0ocd4] index has exceeded [1000000] - maximum allowed to be analyzed for highlighting. #194 (Was from 2.0.0 release, was prio2, but got no attention)
  • exercise config setting index.highlight.max_analyzed_offset (for index has exceeded [1000000] exeption)
• [QA] upgrade from 2.0.0 to 2.1.0 disconnects the elastic host #255
• [QA] search_elastic 2.2.0 has a new admin UI docs-server#101
• [QA] UI maps credentials to a malformed URL, when protocol is specified. #258
• [QA] documentation not linked from admin settings search #259
• [QA] Option 'Scan external storages' cannot be enabled in the web UI once disabled #260 -> [QA] option Scan external storages resets itself (also in v2.0.0) #256
• [QA] search results from contents are always shown 'in another folder' #261
• [QA] search does not start, when using text that was pasted into search field core#39831
• [QA] Trailing whitespace behaviour is confusing #262
• [QA] fast editing in the the searchbox fails to update the search results #263

---

2022-03-17 (RC3)

• [QA] setting a group has no effect #269
• [QA] results from external storages are still shown after disabling scanExternalStorages #270
• https://github.com/owncloud/enterprise/issues/5080

[jnweiger]

Testplan completed with several defects.
Confirmed as blockers:

• [QA] upgrade from 2.0.0 to 2.1.0 disconnects the elastic host #255
• [QA] search_elastic 2.2.0 has a new admin UI docs-server#101
• [QA] Option 'Scan external storages' cannot be enabled in the web UI once disabled #260

[jnweiger]

#255 is not reproducable. Removed from the list of blockers.

[jnweiger]

Re-testing with RC3

• new admin UI elements have choice "No Authentication" and "Username+ and Password"
• admin UI checkbox for external storage does not change after page refresh/reload by itself
• admin UI checkbox for external storage remains in sync with database

See above for additional issues.
No more blocker. Ready to release.

[jnweiger]

Release done. Doc issue still WIP owncloud/docs-server#101