Skip to content
This repository was archived by the owner on Jun 18, 2024. It is now read-only.
This repository was archived by the owner on Jun 18, 2024. It is now read-only.

How to proceed with Bytecoder #12

Description

@keesvandieren

We have done some changes in the Bytecoder project. Therefore we are building our own SNAPSHOT project.

We would like to be based on a release, as this simplifies working with Bytecoder for us

Minimalistic approach

maintainer merges Bytecoder 474. This is really needed to continue without snapshot.

Non-minimalistic approach

We create PRs for all our other changes in Bytecoder as well. With that approach, we have to cope with SNAPSHOT build for longer period of time. And Bytecoder maintainer needs to have time to review and merge.

Advantage is that Bytecoder web APIs will be better, which is an advantage for non-libgdx Bytecoder users.

Actions:

  • Contact Bytecoder maintainer: is he available to review the PRs?
  • depending on outcome, continue with the minimalistic or non-minimalistic approach.

Metadata

Metadata

Assignees

Labels

waitingWaiting for reaction outside team

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions