secdev / secdev/scapy

2.8.0 release

Open
#5,122 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

discussion major
Dominant language
Python
Stars
12.6k
Forks
2.2k
Avg merge
1d 4h
Merged PRs (30d)
56

Description

This issue tracks the upcoming 2.8.0 release.

Expected date: this week (before 05/09 if all goes well)

Deprecation notice
  • This major version will be the last to support Python 3.7 and 3.8. While this was initially planned for 2.7.0, support was extended because of how used those versions still are. They have been EoL for more than 2 years, and we highly encourage remaining users to upgrade.
Note

We have clarified our CONTRIBUTING and SECURITY guidelines. This notably includes some new guidance related to the use of AI, and some instructions regarding the submission of security issues. We encourage contributors to take a moment to read the updated versions.

Changelog

TBD XXX TODO

  • Work has begun to clean up the remaining compatibility code that allowed the transition from Python 2.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with milestone 4 and review the updated CONTRIBUTING and SECURITY guidelines referenced in the issue. Check the pending changelog and the remaining Python 2 compatibility cleanup; the work is done when the 2.8.0 release tracking items are complete and the changelog is no longer marked TBD.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
documentation, release
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.