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.

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

Merged
merged 17 commits into from
Oct 31, 2017
Merged

Adding Change Log #1109

merged 17 commits into from
Oct 31, 2017

Conversation

vsoch
Copy link
Collaborator

@vsoch vsoch commented Oct 27, 2017

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.

  • addition of changelog I have added a changelog, and it dates back to the original 1.x (I did this manually and unfortunately can only grab large details).
  • current PRs I have also added some soon to be merged PRs in development as an example of how we should use it.
  • Updated Contributing: I separated out the sections about contributions (the PR process vs Documentation for it). I made it more clear that documentation should be added along with a note to this log.

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

Copy link
Collaborator

@GodloveD GodloveD left a 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`
Copy link
Collaborator

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?

Copy link
Collaborator Author

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.

Copy link
Collaborator

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
Copy link
Collaborator

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.

Copy link
Collaborator Author

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.

Copy link
Collaborator

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.

Copy link
Collaborator Author

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!

Copy link
Collaborator Author

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:
Copy link
Collaborator

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.

Copy link
Collaborator Author

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.

Copy link
Collaborator

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.

Copy link
Collaborator Author

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)
Copy link
Collaborator

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.

Copy link
Collaborator Author

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.

Copy link
Collaborator

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
Copy link
Collaborator

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)
Copy link
Collaborator

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).

Copy link
Collaborator Author

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**
Copy link
Collaborator

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.

Copy link
Collaborator Author

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!

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator

@GodloveD GodloveD left a 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?

@vsoch
Copy link
Collaborator Author

vsoch commented Oct 31, 2017

Sure thing! I'll wait for it to turn green. My trust in Travis consistency is... squishy at best.

@vsoch
Copy link
Collaborator Author

vsoch commented Oct 31, 2017

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!

@vsoch vsoch merged commit 3dda9a9 into apptainer:development Oct 31, 2017
gmkurtzer pushed a commit that referenced this pull request Nov 10, 2017
* 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.
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.

5 participants