automate the release process

Open
#59 7 comments 0 reactions 1 assignee View on GitHub

@glennklockwood is already working on this.

Since Jun 24, 2020.

Assessment

This issue has not been assessed yet.

Description

bug

I just downloaded the 3.1.0.tar.gz tarball, and it doesn't have a configure script in it. The zip file is also missing it. I can generate the configure script using the bootstrap script, but not on all of my machines as my autotools isn't new enough everywhere. I can create a tarball with the configure script in it by running 'make dist', so the capability is still there.

Is not including the configure script in release archives going to be normal now? If that is the case, it might be worthwhile to update the README file with the proper directions for building (running bootstrap is required) and information on the proper versions of autotools to use.

Thanks!
David

Dominant language
C
Stars
487
Forks
200
Avg merge
1d 21h
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hpc/ior

All issues in hpc/ior

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.