Tags

v0.2.0: First CRAN release

This is the first release successfully submitted to CRAN.
The purpose of the v0.2.0 release is to ensure that `calendRio` meets
the CRAN requirements before moving towards a 1.0 release that actually
adds functionality on top of the upstream `calendR` package.

This version was reviewed for CRAN by Julia Haider [JH], Uwe Ligge [UL],
and Gregor Seyer [GS].

Changes since v0.1.0 [requested by CRAN reviewer]:

* Documentation:
  * Add header comments.
  * Re(/sub-)license: MIT -> AGPL-3.0-or-later.
  * Drop Markdown link from package title.
  * Fix `mailto:` link in README Markdown file.
  * Link to license file copy visible to CRAN.
  * Wrap link in DESCRIPTION in angle brackets.
  * Extend package description. [JH]
  * Document return value of `calendR` function. [JH]
  * Fix package description formatting. [UL]
  * Extend package title. [UL]
  * Remove CRAN reviewers from author list. [JH]

* Chores:
  * Bump version to 0.2.0.

v0.2.0-rc6: 6th RC for CRAN submission test

This is the sixth release candidate to be submitted to CRAN.
The purpose of the v0.2.0 release is to ensure that `calendRio` meets
the CRAN requirements before moving towards a 1.0 release that actually
adds functionality on top of the upstream `calendR` package.

Release candidates are tagged on the corresponding release branch
(branched off from the development branch) before merging to the main
branch. This allows for additional fixes before the actual release.
Once the new version was successfully submitted to (and accepted by)
CRAN, the release branch is merged to the main branch and the resulting
merge commit is tagged as release.

This RC addresses all remarks by CRAN reviewer Julia Haider concerning
`calendRio` version 0.2.0-rc5.

Changes since v0.2.0-rc5:

* Documentation:
  * Remove CRAN reviewers from author list

v0.2.0-rc5: 5th RC for CRAN submission test

This is the fith release candidate to be submitted to CRAN.
The purpose of the v0.2.0 release is to ensure that `calendRio` meets
the CRAN requirements before moving towards a 1.0 release that actually
adds functionality on top of the upstream `calendR` package.

Release candidates are tagged on the corresponding release branch
(branched off from the development branch) before merging to the main
branch. This allows for additional fixes before the actual release.
Once the new version was successfully submitted to (and accepted by)
CRAN, the release branch is merged to the main branch and the resulting
merge commit is tagged as release.

This RC tries to address all remarks by CRAN reviewer Uwe Ligge
concerning `calendRio` version 0.2.0-rc4.

Changes since v0.2.0-rc4:

* Documentation:
  * Fix package description formatting
  * Extend package title

v0.2.0-rc4: 4th RC for CRAN submission test

This is the fourth release candidate to be submitted to CRAN.
The purpose of the v0.2.0 release is to ensure that `calendRio` meets
the CRAN requirements before moving towards a 1.0 release that actually
adds functionality on top of the upstream `calendR` package.

Release candidates are tagged on the corresponding release branch
(branched off from the development branch) before merging to the main
branch. This allows for additional fixes before the actual release.
Once the new version was successfully submitted to (and accepted by)
CRAN, the release branch is merged to the main branch and the resulting
merge commit is tagged as release.

This RC tries to address all remarks by CRAN reviewer Julia Haider
concerning `calendRio` version 0.2.0-rc3.

Changes since v0.2.0-rc3:

* Documentation:
  * Extend package description
  * Document return value of `calendR` function

v0.2.0-rc3: 3rd RC for CRAN submission test

This is the third release candidate to be submitted to CRAN.
The purpose of the v0.2.0 release is to ensure that `calendRio` meets
the CRAN requirements before moving towards a 1.0 release that actually
adds functionality on top of the upstream `calendR` package.

Release candidates are tagged on the corresponding release branch
(branched off from the development branch) before merging to the main
branch. This allows for additional fixes before the actual release.
Once the new version was successfully submitted to (and accepted by)
CRAN, the release branch is merged to the main branch and the resulting
merge commit is tagged as release.

Changes since v0.2.0-rc2:

* Documentation:
  * Fix `mailto:` link in README Markdown file
  * Link to license file copy visible to CRAN
  * Wrap link in DESCRIPTION in angle brackets

v0.2.0-rc2: 2nd RC for CRAN submission test

This is the second release candidate to be submitted to CRAN.
The purpose of the v0.2.0 release is to ensure that `calendRio` meets
the CRAN requirements before moving towards a 1.0 release that actually
adds functionality on top of the upstream `calendR` package.

Release candidates are tagged on the corresponding release branch
(branched off from the development branch) before merging to the main
branch. This allows for additional fixes before the actual release.
Once the new version was successfully submitted to (and accepted by)
CRAN, the release branch is merged to the main branch and the resulting
merge commit is tagged as release.

Changes since v0.2.0-rc1:

* Documentation:
  * Drop Markdown link from package title

v0.2.0-rc1: 1st RC to test CRAN submission

This is the first release candidate to be submitted to CRAN.
The purpose of the v0.2.0 release is to ensure that `calendRio` meets
the CRAN requirements before moving towards a 1.0 release that actually
adds functionality on top of the upstream `calendR` package.

Release candidates are tagged on the corresponding release branch
(branched off from the development branch) before merging to the main
branch. This allows for additional fixes before the actual release.
Once the new version was successfully submitted to (and accepted by)
CRAN, the release branch is merged to the main branch and the resulting
merge commit is tagged as release.

Changes since v0.1.0:

* Documentation:
  * Add header comments
  * Re(/sub-)license: MIT -> AGPL-3.0-or-later
* Chores:
  * Bump version to 0.2.0

v0.1.0: Initial (minimal) test release

This is a first test release.
It marks the first version of `calendRio` after branching off the
upstream `calendR` R package that passes both

```sh
reuse lint
```

and

```R
devtools::check()
```

This version of `calenRio` does not yet provide any new functionality on
top of `calendR` and is therefore not meant to be submitted to CRAN or
distributed for installation in any other way.

Changes since branching off from upstream `calendR` R package:

* Documentation:
  * Satisfy REUSE specifications (v3.0)
  * Remove `.github` directory
  * Remove package startup message hook
  * Rename fork
  * Add DESCRIPTION file
  * Symlink LICENSE to top-level directory
  * Generate documentation with `roxygen2`
  * Add imports to DESCRIPTION
  * Use 'family' rather than 'last' name
* Chores:
  * Remove auto-generated by `roxygen2`
  * Remove `DESCRIPTION` file
  * Remove `.gitignore` file
  * Remove package documentation
  * Hide non-standard files in `inst` directory

Branch point from upstream `calendR` R package

This is the last commit of the `calendR` R package before the
`calendRio` fork started diverting from it.
Thus, this tag can be used to identify code that is exclusive to the
fork.