#841 closed but not merged to current release

Open
#877 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
databases

Research direction

Inspect commit dcfa3ae on the release-3.0 branch and compare it with the current upstream release. Check whether it addresses the reported Java API compatibility issue, then verify that the fix is included in the released code. No specific files or tests are named in the issue.

Written by the indexing model from the issue text.

Description

3.0 document

It seems to me, the commit dcfa3ae in the branch release-3.0 solves a major issue in terms of compatibility with the Java API, but was never released.

Any reasons, not to cherry-pick that commit to upstream and fix the bug?

Dominant language
Java
Stars
5.1k
Forks
877
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from jankotek/mapdb

All issues in jankotek/mapdb

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.