build these. Not invoked automatically though, since these should very
rarely conflict and we don't want to have version build difference
conflicts (harmless) all the time.
Generate intermediate rst file instead of html
Move generation to doc/Makefile
Use pandoc to generate table of contents and fragment ids.
Remove nested inline markup (not supported by reStructuredText)
Fix https and other links.
+ the plumbing for slides creation
Init of #2244, second part: Python converter md to html + wip on GCC 2015 talk conversion
Add the 2. Galaxy app architecture. Need images
Add the 3. Galaxy components and object model
Add more content in md
Fix linting error by adding newline at the end of build_slideshow.py
Moved the galaxyArchitecture.md into a folder dedicated to it
Add 7th and 17th image + add style.css to have a better management of layout + added first slide as the first in GCC2015 slide
Set properly the CSS used in the whole presentation + add special to p and first slide
Add special orange for regular text and green emphasis (emphasis_2_galaxy)
Changed the font to PT Sans
Add 3. with images + few modifications
Removed the images integrated using background-image by now Markdown imaging (still need work, image's size seems not good by default
Add Makefile target to build architecture slides...
2016 Updates to 2015 architecture talk.
More intro slides for Galaxy architecture.
Update author line.
Progress on architecture slides...
- Improved styling (use Oxygen - closer to Galaxy font)
- Add ability to generate SVG diagrams to slide infrastructure
- Add newer client-server sequence diagram based on that.
Improved logging when there are problems with SQL migrations.
More misc work on architecture talk.
More images, slides, slide formatting, and initial work on an IPython notebook.
Improved styling for architecture slides...
Updates to architecture talk...
- Infrastructure for building class diagrams with plantuml
- Bring in move SVGs from last year's google docs.
- Fill out section on client architecture.
More work on slides for architecture talk.
Add startup_output.
Replace mermaid diagrams with plantuml diagrams.
Fill out these diagrams more and style them for a black background in Galaxy oranges.
the client. Execute in parallel, which is super handy, using something
like `make -j webpack-watch grunt-watch-style grunt-watch-develop`.
Make sure to rerun the root `make client` before committing though!
doesn't understand an empty '' in-place extension the same way. So,
fixed one, broke the other.
This approach with the -e argument feels like a total hack since it
explits the fact that bsd sed consumes the -e as the argument to -i, but
it still has the command interpreted correctly.
upstream is used repeatedly and just assumed to be a remote - this tests for it and adds it if it doesn't exist before using in make commands now. This also automates the previous release to dev merge in the instructions with a new Make command.
Additionally, two PRs need to be created to update versions. This prints a reminder to do this and adds it to the release checklist. Ideally, these PRs could be avoided with a direct push or automatically created with hub (https://github.com/github/hub).
Create new makefile targets for release management.
- ``release-create-issue``: Automates creating a release checklist - https://github.com/jmchilton/galaxy/issues/41)
Check list contains actual tailored ``make`` commands and links (for PRs and issues).
- ``release-check-metadata``: Checks milestone PRs for required metadata needed for generating bootstrapped release notes.
` ``release-bootstrap-history``: Bootstrap release notes from PRs and metadata.
- ``release-check-blocking-prs``: Check for PRs blocking release, should happen before branching release and before tagging release.
- ``release-check-blocking-issues``: Check for Issues blocking release, should happen before tagging release. (Only allowed issue is the release creation issue.)
The issue created with ``release-create-issue`` documents how and when to execute subsequent ``make`` targets (including the target to create the issue for the next release).
This PR contains a bunch of other enhancements to the bootstrap_history.py script to enable these targets and renames ``create_release_rc`` Makefile target so all release related targets start with the prefix ``release-``.
Conflicts:
Makefile
John Chilton