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

Publication of Galaxy Release v 16.01 #39

Open
3 of 36 tasks
jmchilton opened this issue Jan 26, 2016 · 0 comments
Open
3 of 36 tasks

Publication of Galaxy Release v 16.01 #39

jmchilton opened this issue Jan 26, 2016 · 0 comments

Comments

@jmchilton
Copy link
Owner

  • Prep
    • Create this release issue make release-issue RELEASE_CURR=16.01.
    • Set freeze date (2016-01-04).
  • Branch Release (on or around 2016-01-04)

    • Review milestone PRs and delay or merge or close each. Link

    • Merge the latest release into dev.

      git fetch upstream && git checkout dev && git merge --ff-only upstream dev && git merge upstream release_15.10

    • Create and push release branch:

      make create_release_rc RELEASE_CURR=16.01 RELEASE_NEXT=16.04
  • Deploy and Test Release
    • Deploy to test (2016-01-04 + 1 day).
    • Deploy to usegalaxy.org (2016-01-04 + 1 week).
  • Create Release Notes

    • Ensure all blocking PRs have been merged or closed. Link

      make release-check-blocking-prs RELEASE_CURR=16.01

    • Checkout release branch

      git checkout 16.01 -b 16.01_release_notes

    • Check for obvious missing metadata in release PRs

      make release-check-metadata RELEASE_CURR=16.01

    • Bootstrap the release notes

      make release-bootstrap-history RELEASE_CURR=16.01

    • Open newly created files and manually curate major topics and release notes.

    • Commit release notes.

      git add docs/; git commit -m "Release notes for 16.01"; git push upstream 16.01_release_notes

    • Open a pull request for new release note branch.

    • Merge release note pull request.

  • Do Release

    • Ensure all blocking issues have been resolved. Link

      make release-check-blocking-issues RELEASE_CURR=16.01

    • Ensure all blocking PRs have been merged or closed. Link

      make release-check-blocking-prs RELEASE_CURR=16.01

    • Do release (TODO: create a check a list for this...)

  • Announce Release
  • Prepare for next release
    • Ensure milestone 16.04 exists.
    • Create release issue for next version make release-issue RELEASE_CURR=16.04.
    • Close this issue.
jmchilton pushed a commit that referenced this issue Jul 27, 2016
@bwlang @mvdbeek
WIP re #39 - run dependency management during repository installation
fd9eb82 
working:
	- fetching valid tool list
	- identifying unique requirements

not working:
	File '/Users/langhorst/src/galaxy_hackathon/lib/galaxy/webapps/galaxy/controllers/admin_toolshed.py', line 1138 in prepare_for_install
  [view.manager_dependency(req) for req in uniq_reqs.values()]
TypeError: manager_dependency() takes exactly 1 argument (2 given)
jmchilton pushed a commit that referenced this issue Jan 22, 2018
@bgruening
Merge pull request #39 from mvdbeek/bam_unsorted
d544adf 
Fix tests and revert additional sorting of converters
jmchilton pushed a commit that referenced this issue Apr 17, 2018
@dannon
Merge pull request #39 from guerler/fix_dropdown_grids
21b700b 
Fix dropdown operations buttons and pagination links in grids
jmchilton pushed a commit that referenced this issue Nov 17, 2021
@mvdbeek
Fix action token sending for chracters that are escaped in html
48d5431 
The function body of escape is
```
def escape(s):
    """Replace the characters ``&``, ``<``, ``>``, ``'``, and ``"`` in
    the string with HTML-safe sequences. Use this if you need to display
    text that might contain such characters in HTML.

    If the object has an ``__html__`` method, it is called and the
    return value is assumed to already be safe for HTML.

    :param s: An object to be converted to a string and escaped.
    :return: A :class:`Markup` string with the escaped text.
    """
    if hasattr(s, "__html__"):
        return Markup(s.__html__())
    return Markup(
        text_type(s)
        .replace("&", "&amp;")
        .replace(">", "&gt;")
        .replace("<", "&lt;")
        .replace("'", "&#39;")
        .replace('"', "&#34;")
    )
```
It doesn't make sense to lookup the replaced values in the database,
and it breaks single-quotes in the email username portion, which is
valid https://en.wikipedia.org/wiki/Email_address#Syntax
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jmchilton