-
Notifications
You must be signed in to change notification settings - Fork 424
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
Adding Change Log #1109
Adding Change Log #1109
Conversation
Force NULL terminator into tf->filename to avoid buffer overflow
alpine ABUILD for versions 2.3.2 and 2.4
in order to make package builds reproducible. See https://reproducible-builds.org/ for why this is good. Requires GNU tar-1.28 or later to be reproducible Using gzip -n to not add a timestamp to the .gz header
Make tar file creation reproducible
Revert "Make tar file creation reproducible"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vsoch Thank you for putting this together! A lot of good work in a short period of time. For the most part this looks great. I have some small nitpicky comments, but overall it's just what we need.
@@ -3,7 +3,7 @@ | |||
|
|||
## Code | |||
- [] Ensure docs exist at singularityware.github.io for new/updated features | |||
- [] Update version number in `configure.ac` | |||
- [] Update version number in `configure.ac` and `INSTALL.md` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this supposed to be here? Does it conflict with #1112?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They are different things - that PR adds it to the debian install files, and this one is general configuration of Singularity.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK thanks.
@@ -11,6 +11,7 @@ For issues with code (and especially if you need to share debug output) we recom | |||
|
|||
- [Singularity Issues](https://github.com/singularityware/singularity/issues): is recommended for most issues with the Singularity software. | |||
- [Singularity Hub Issues](https://github.com/singularityhub/singularityhub.github.io/issues): is the board for issues relevant to Singularity Hub. | |||
- [Singularity Registry Issues](https://github.com/singularityhub/sregistry/issues): is the board for issues relevant to Singularity Registry |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should really be Singularity Hub right? There may be many Singularity Registries but there is only shub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, lol. Singularity Registry is a different thing :)
https://github.com/singularityhub/sregistry
it's even peer reviewed / published!
http://joss.theoj.org/papers/050362b7e7691d2a5d0ebed8251bc01e
it's times like these the stuff I do feels... totally unnoticed lol.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh sorry. I thought shub was a special case of a Singularity registry. Nevermind.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's like homo sapiens and Neanderthal. Maybe some wayward, back in the day common elements (mostly UI) but different beasties under it all!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but yeah Shub (which came first) does deliver the common API endpoints of a registry so Shub works like one too. It's the mamma registry! The HUB.
CHANGELOG.md
Outdated
Each section should include general headers such as **Implemented enhancements** | ||
and **Merged pull requests**. All closed issued and bug fixes should be | ||
represented by the pull requests that fixed them. This log originated with Singularity 2.4 | ||
and changes prior to that are (unfortunately) done retrospectively. From @olifre, critical items to know are: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems sort of weird to shout out olifre here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why? It's his statements. If I don't it's plagarism.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because this is basically documentation and it seems unprofessional. But if you feel that you would be a plagiarist without the proper citation I won't argue. I don't feel strongly about it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed it! 5 hours ago :)
CHANGELOG.md
Outdated
- changed behaviour (recipe sections work differently) | ||
|
||
|
||
## [v3.0](https://github.com/singularityware/singularity/tree/development) (development) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should probably be 2.4.1 not 3.0.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gmkurtzer said the next "official" version is 3.0, but I suppose we didn't plan for the bug fixes. I'll change it if it makes you happy.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's either that or go without a changelog in 2.4.1. 😺
CHANGELOG.md
Outdated
- This changelog was added. | ||
|
||
**Bug Fixes** | ||
- .wh.* files leading to permissions errors from Docker aufs extractions are skipped on extraction |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's keep changes out until they are actually merged. Otherwise we get into a situation where the changelog represents hopes instead of reality.
CHANGELOG.md
Outdated
**Deprecated** | ||
- the `create` command is being deprecated in favor of `image.create` | ||
- `bootstrap` is being deprecated in favor of `build` (will work through 2.4) | ||
- `expand` is being deprecated, as a container can be used as a build base to change it (will work through 2.4) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
was deprecated in favor of image.expand and no longer works on images with headers (i.e. after they are built).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
CHANGELOG.md
Outdated
## [v2.3.2](https://github.com/singularityware/singularity/tree/v2.3.2) (2017-09-15) | ||
[Full Changelog](https://github.com/singularityware/singularity/compare/2.3.1...2.3.2) | ||
|
||
**Implemented enhancements** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer if we used 3 hashes instead of bold to delineate subheadings in keeping with markdown syntax. And as an added bonus things will work better in the future if we ever decide to add a toc and put it up online or something.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
aye aye cap-i-tan!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me. @gmkurtzer said we can go ahead and merge this when ready. So I think it's ready. Can you squash the commits or whatever and merge?
Sure thing! I'll wait for it to turn green. My trust in Travis consistency is... squishy at best. |
Travis is being wanky, so since there isn't actually any code to test, I'm going to squash and merge. Onwards to a new beginning with better documentation, long live CHANGELOG.md! |
* updating support, contributing, and adding changelog * modified: .github/PULL_REQUEST_TEMPLATE.md * removing files * removing weird extra files * keeping old files so still builds * changing... the CHANGElog. So many changes.
Description of the Pull Request (PR):
This PR is an effort to start being better at keeping track of changes, deprecation, and all of these import usage details that are essential for users.
I fixed some other small bugs, but the important thing for discussion here is the changelog. I still have no idea why the extra files for @truatpasteurdotfr are here, I can only guess it was some Github error that now remains in development. As with the other PR, please let me know to remove this or not.
This fixes or addresses the following GitHub issues:
Attn: @singularityware-admin