Tracking issue for the 4.0.0 release
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
Read the linked pull requests, starting with #2066, which the issue marks as required for the release. The issue tracks several release decisions and nearly completed changes but does not identify a specific implementation task for a newcomer. Done means the required release work is resolved and the 4.0.0 release can be cut.
Written by the indexing model from the issue text.
Description
Hi all!
I'm starting this issue to track tasks for the next release.
This is the list of pending issues that I think that should be resolved before we cut the next release:
- https://github.com/apache/libcloud/pull/2066 -> Must be in this new release
- https://github.com/apache/libcloud/pull/2061
- https://github.com/apache/libcloud/pull/2124
- https://github.com/apache/libcloud/pull/2125
- https://github.com/apache/libcloud/pull/2127 -> Not sure about it.
- https://github.com/apache/libcloud/pull/2189 -> Almost done
- https://github.com/apache/libcloud/pull/2199 -> Almost done
cc @tisonkun @Kami @PsiACE
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 935
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 15
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/libcloud
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Local range download leaves an output file after source-read failure despite delete_on_failure=TrueOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
Maintainers usually reply within 1 day
Similar issues
-
Email validation accepts a trailing newlinePossibly taken @marcello-pichini claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dbt-labs/spark-utils#51 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
bug frontend
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
vendrabuck/HERD#1419 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day