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.

Sign up for GitHub

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

Jump to bottom

Strategy for developing jp2gen and SSW #35

Open
wafels opened this issue Mar 17, 2022 · 0 comments
Open

Strategy for developing jp2gen and SSW #35

wafels opened this issue Mar 17, 2022 · 0 comments
Assignees
@jonltsang3
Labels
enhancement

Comments

@wafels
Copy link
Contributor

wafels commented Mar 17, 2022

jp2gen uses git/github.com for development, and SSW uses a separate non-git process.

I think git/github.com should be used to develop jp2gen specific code. SSW should use its own process separately.

Every night jp2gen can be pulled in to SSW so the SSW version is up to date, and SSW users don't have to use the git version.

Thoughts?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jonltsang3 jonltsang3

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wafels @jonltsang3