by adom

Interactive Gantt chart viewer for project timelines, with a table view and an analytics page over the same data. Data-driven, dark by default with a print-friendly light mode, and fully editable in the browser: drag bars to move or resize, multi-select and batch-shift dates, manage dependency arrows inline, reorder rows, filter by phase, and undo. One click auto-schedules the whole plan so every dependency lines up finish-to-start on working days, skipping weekends and US federal holidays, push

Overview Files Skills Discover Packages Releases Dependencies Issues Breadcrumbs Pull Requests Activity

master

History Download

Drew Owens Docs: the what-lives-where diagram on the main page, updated for 0.77.1 (one Owner filter for both lenses, field-by-fie… 759bca6 11d ago

Releasing adom-gantt

The list for every version. What changed and why goes in BUILD-NOTES.md.

Version. Bump version in package.json and page.json.
Gates, one after another. node test/server_test.mjs, node test/collab_test.mjs, then node test/ui_test.mjs. Never two at once: they share test ports. When several people or agents run suites on one machine, wrap each run in the same flock lock file.
What lives where. If the release changes what stays in a tab, in the browser or on the server (a filter, a setting, how saving or catching up works), update client-vs-server/where-it-lives.html and the tables in client-vs-server/README.md, re-render the PNG with node test/render-diagram.mjs, and look at the PNG. The main README shows it under "Your view and the shared plan: what lives where"; check it still does.
Build notes. A new entry at the top of docs/BUILD-NOTES.md: what changed, why, and the test counts.
Publish. adom-wiki pkg info adom/adom-gantt first, in case another session published; then adom-wiki pkg publish --org adom -y, and adom-wiki repo push for anything the package leaves out. Check a fresh clone and the live page.
Deploy. Only with the plan owner's go. A changed server.js needs a restart; a changed page needs only the files. Either way, everybody with the plan open reloads once.

# Releasing adom-gantt

The list for every version. What changed and why goes in [BUILD-NOTES.md](BUILD-NOTES.md).

1. **Version.** Bump `version` in `package.json` and `page.json`.
2. **Gates, one after another.** `node test/server_test.mjs`, `node test/collab_test.mjs`,
   then `node test/ui_test.mjs`. Never two at once: they share test ports. When several
   people or agents run suites on one machine, wrap each run in the same `flock` lock file.
3. **What lives where.** If the release changes what stays in a tab, in the browser or on
   the server (a filter, a setting, how saving or catching up works), update
   `client-vs-server/where-it-lives.html` and the tables in `client-vs-server/README.md`,
   re-render the PNG with `node test/render-diagram.mjs`, and look at the PNG. The main
   README shows it under "Your view and the shared plan: what lives where"; check it still
   does.
4. **Build notes.** A new entry at the top of `docs/BUILD-NOTES.md`: what changed, why,
   and the test counts.
5. **Publish.** `adom-wiki pkg info adom/adom-gantt` first, in case another session
   published; then `adom-wiki pkg publish --org adom -y`, and `adom-wiki repo push` for
   anything the package leaves out. Check a fresh clone and the live page.
6. **Deploy.** Only with the plan owner's go. A changed `server.js` needs a restart; a
   changed page needs only the files. Either way, everybody with the plan open reloads once.

Adom Gantt

Releasing adom-gantt