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

Start Deprecation and Removal of Selenium2Library (deep) references/package #1826

Closed
emanlove opened this issue May 17, 2023 · 7 comments
Closed
Assignees
Labels
Milestone

Comments

@emanlove
Copy link
Member

As noted in the v6.1.0 release notes .. "Due to the issues around upgrading packages and the simple passage of time, it is time to depreciate and remove the Selenium2Library package." This issue will track the task and progress of the depreciation.

@emanlove emanlove added this to the V6.2.0 milestone May 17, 2023
@humbienri
Copy link
Contributor

;) Depreciation or deprecation is it?

@emanlove
Copy link
Member Author

emanlove commented May 17, 2023

Oh .. darn. Now I am trying to remember if I was saying the right word that entire meeting. Thanks for noting this @humbienri Corrected.

@emanlove emanlove changed the title Start Depreciation and Removal of Selenium2Library (deep) references/package Start Deprecation and Removal of Selenium2Library (deep) references/package May 17, 2023
@humbienri
Copy link
Contributor

I was only kidding! I don't do much RF work at all anymore but I still get the GH emails about it. Ya'll are a great bunch of folks! One of the best online communities I've EVER seen. Kudos!

@emanlove
Copy link
Member Author

Well we definitely don't want to devalue it over time (depreciate) but instead we want to discourage current usage, encourage people instead to use SeleniumLibrary directly and plan a removal (deprecate). So I think you got it right. And thanks for the kind words :)

@humbienri
Copy link
Contributor

humbienri commented May 17, 2023

Actually, I am surprised to see S2L still around! Like I said, it's been years since I used RF-anything and even back then I thought S2L needed to go and its usage should have been highly discouraged. So I do think you are doing the right thing; alleviating some of the burden from ya'll's backs. Best of luck Ed!

@emanlove
Copy link
Member Author

emanlove commented May 18, 2023

Some initial thoughts on the steps to Start Deprecation and Removal of Selenium2Library (deep) references/package

Stage 1

  • - Make announcements everywhere (Slack, Forum, LinkedIn, Twitter, Facebook, email lists) ..
  • - Add note to install saying this is deprecated and will be removed in the near future(? specifics)
  • - Move "Versions" and "History" sections of README.rst to VERSIONS.rst referencing this file.
  • - Remove Selenium2Library instructions moving them to this new versions.rst file.
  • - Update setup.py
  • - [It may be possible to get the list of projects that use Selenium2Library from GitHub. Last check Used By shows 1,159 repositories so it is not clear what one would do with this information. And how to discern out which repos are old. I know this can be done but the amount of work to do that now might be questionable in terms of ROI]
  • [ ]

Stage 2

  • Add note to install saying this will be removed on xx/xx/2023 date

Stage 3

  • Add error to install causing install to fail

Stage 4 (?)

  • Deal with cleanup mess

@emanlove
Copy link
Member Author

We have started some documentation changes which have been merged into master for the upcoming v6.4.0 release. One last change I wanted to get in was provide from the SeleniumLibrary side a warning if it was wrapped by Selenium2Library but having some issues with my IDEs. I am going to open another issue for that so that we can close this and recognize some work has been done to deprecate Selenium2Libary.

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

No branches or pull requests

2 participants