8000 run create_RELEASES on newly generated release by tsloughter · Pull Request #48 · erlware/relx · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Dismiss alert

run create_RELEASES on newly generated release #48

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.

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

Merged
merged 4 commits into from
Sep 21, 2013
Merged

Conversation

tsloughter
Copy link
Member

On important reason for this change is to allows for downgrading to the initial release. This is not possible currently because it's contents in the RELEASES file created when you upgrade to a newer version of the release does not contain the necessary information for the initial version to allow downgrading.

@ericbmerritt
Copy link
Member

If you are submitting these @tsloughter please drop the merge commits.

RJ and others added 3 commits September 20, 2013 20:07
The "bin/RELNAME install" command now handles upgrading and downgrading.
It unpacks and installs new versions as needed, or just sets existing
releases as current/permanent as needed.

I renamed from "bin/RELNAME upgrade" because it handles downgrades too.
"upgrade" and "downgrade" are now synonyms for "install"

Additionally, when installing a new to-be-unpacked version, you can say:

  bin/RELNAME install 0.1.1/beat

OR just:

  bin/RELNAME install 0.1.1

in which case the /RELNAME part is added automatically. This is to keep
the version spec for downgrades the same as for new upgrades.

This is fully backwards compatible with the existing "upgrade" command.
tsloughter added a commit that referenced this pull request Sep 21, 2013
run create_RELEASES on newly generated release
@tsloughter tsloughter merged commit 2ef124b into master Sep 21, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0