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

Minimal Firefox Support #14015

Closed
7 tasks done
slemeur opened this issue Jul 25, 2019 · 5 comments
Closed
7 tasks done

Minimal Firefox Support #14015

slemeur opened this issue Jul 25, 2019 · 5 comments
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
Milestone

Comments

@slemeur
Copy link
Contributor

slemeur commented Jul 25, 2019

Goal

Eclipse Che is validated on Google Chrome, but should support (and be usable) from other web browsers.

The goal of this epic is to analyze and detail the requirements on providing a minimal support for Firefox.

Related issues

@slemeur slemeur added the kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. label Jul 25, 2019
@slemeur slemeur added this to the 7.2.0 milestone Jul 25, 2019
@gazarenkov gazarenkov removed this from the 7.2.0 milestone Oct 2, 2019
@ibuziuk ibuziuk added this to the Backlog - Epics milestone Oct 30, 2019
@AndrienkoAleksandr
Copy link
Contributor

I lived some comment about minimal supported Firefox version #13442 (comment)

@ibuziuk ibuziuk added the status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. label Dec 9, 2019
@azatsarynnyy azatsarynnyy mentioned this issue Dec 18, 2019
8 tasks
@azatsarynnyy
Copy link
Member

@slemeur I'm not sure that this one is related to the epic
Deprecate the obsolete versions of OpenShift and Kubernetes plugins #15140

I'll exclude it. Are you agree?

@azatsarynnyy
Copy link
Member

Closing it as all the issues are solved.

@nickboldt
Copy link
Contributor

nickboldt commented Jan 21, 2020

To make it easier to know when a feature is implemented, please make sure when you close an issue it's not still in the backlog, but in the sprint/fixversion/milestone in which it's delivered.

Assuming based on date that this was done for 7.7.

@azatsarynnyy
Copy link
Member

Thanks, @nickboldt! I'll take it into account.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
Projects
None yet
Development

No branches or pull requests

6 participants