Steps required for publishing package · maxGraph/maxGraph · Discussion #41
It would be good to release a new jsGraph/mxgraph package on npmjs.com so that Threat Dragon and other projects can start to migrate away from using jGraph/mxgraph.
As I see it the steps required to do this are:
- fix on a name, as discussed in Rename the project, licensing issue with name "mxGraph" #23
- rename jsGraph/mxgraph github repository to jsGraph/new-name - Done: maxGraph/maxGraph
- decide on what the version should be. It has been proposed that version 5.0 is good
- create a branch from which we can publish to npmjs.com
- from @lreading 's comment below, wind back this branch to a clean licence version
- publish max-graph/maxGraph on npmjs.com
- nice to have a note on the existing jGraph/mxgraph package that it has been superseded - would need permissions
The Threat Dragon and other projects can start using the new package
Will this package be made from the development branch or main branch?
I think another step before publishing the package would be reverting a few commits to ensure that the licensing issues are addressed. I can open an issue for that if we need.
It's also worth noting that a deprecated notice has been placed on the mxgraph package.
1 reply
Hi, the package will be made from the development branch.
There are some pending works in a dedicated branch that contains the migration to Typescript, tree shaking capacities and more. See #51 for more details.
hi buddy, how are things going with the package release? We sincerely hope that this project can move on, so what can I do for these steps ？
1 reply
hi buddy, how are things going with the package release? We sincerely hope that this project can move on, so what can I do for these steps ？
2 replies
See #41 (comment)
Next time, please avoid duplicating comments, put a reply on existing comments instead. This will avoid the spammy effect.