hoe-manns

code

launchpad.net/hoe-manns

rdoc

www.rubydoc.info/gems/hoe-manns

docs

saigkill.github.io/hoe-manns/about/

bugs

bugs.launchpad.net/hoe-manns

questions

answers.launchpad.net/hoe-manns

feature requests

blueprints.launchpad.net/hoe-manns

openhub statistics

www.openhub.net/p/hoe-manns

authors blog

saigkill.tuxfamily.org

min_rubyver

2.3.0

If you're reading this on Github, please keep in mind, that this is just a mirror. The development happens on: launchpad.net/hoe-manns

DESCRIPTION:

hoe-manns is a small collection of my personal used rake tasks for using with hoe. Actually it includes that tasks:

  • bundler:gemfile_lock

  • bundle_audit:*

  • clean_pkg

  • copy_master

  • remove_pre_gemspec

  • run_before_release

  • run_after_release

The History.rdoc contains a detailed description on what has changed. For most users the NEWS file might be a better place to look since it contains change summaries between the different versions.

hoe-manns is released under the GPL3 License, see the file 'License.rdoc' for more information.

The official web site is:

https://launchpad.net/hoe-manns

FEATURES/PROBLEMS:

  • Updates the Gemfile.lock

  • Removes the old *.gemspec created in test cases

  • copies your manuals to your docpath.

  • runs the rake tasks before release: git:manifest, bundler:gemfile, update_gemfile_lock, remove_pre_gemspec,

bundler_audit:run and copy_mirror.

  • runs after release: send_email.

  • Cleans up the pkg dir

  • provides bundler_audit tasks

This Gem was programmed and tested for Linux systems. If anyone would like to make the methods also fit for other OS, i'm happy about Pull requests.

See the FAQs for checking known issues. See the status of the app.

SYNOPSIS:

Use in your Rakefile:

Hoe.plugin :manns

Hoe.spec 'yourproject' do
...
end

Also add hoe-manns to your requirements and recreate your Gemfile.

Read the documentation at: saigkill.github.io/hoe-manns/about/

REQUIREMENTS:

  • rake

  • hoe

  • bundler-audit

INSTALL:

The installation is very easy.

gem install hoe-manns

Read the documentation at: saigkill.github.io/hoe-manns/about/

DEVELOPERS:

After checking out the source, run:

$ rake newb

This task will install any missing dependencies, run the tests/specs, and generate the RDoc.

IDEAS:

COOL HACKS:

  • Open a bugreport on bugs.launchpad.net/hoe-manns.

  • Please use the -u flag when generating the patch as it makes the patch more readable.

  • Write a good explanation of what the patch does.

  • It is better to use git format-patch command: git format-patch HEAD^

CONTRIBUTOR CODE OF CONDUCT:

As contributors and maintainers of this project, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.

We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, age, or religion.

Examples of unacceptable behavior by participants include the use of sexual language or imagery, derogatory comments or personal attacks, trolling, public or private harassment, insults, or other unprofessional conduct.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct. Project maintainers who do not follow the Code of Conduct may be removed from the project team.

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by opening an issue or contacting one or more of the project maintainers.

This Code of Conduct is adapted from the Contributor Covenant, version 1.0.0, available at contributor-covenant.org/version/1/0/0/.

MAINTANANCE POLICY:

I'm following the Semantic Versioning for its releases: (Major).(Minor).(Patch).

* Major version: Whenever there is something significant or any backwards
  incompatible changes.
* Minor version: When new, backwards compatible functionality is introduced a
  minor feature is introduced, or when a set of smaller features is rolled out.
* Patch number: When backwards compatible bug fixes are introduced that fix
  incorrect behavior.
* The current stable release will receive security patches and bug fixes
  (eg. 5.0 -> 5.0.1).
* Feature releases will mark the next supported stable release where the minor
  version is increased numerically by increments of one (eg. 5.0 -> 5.1).

I encourage everyone to run the latest stable release to ensure that you can easily upgrade to the most secure and feature rich experience. In order to make sure you can easily run the most recent stable release, we are working hard to keep the update process simple and reliable.

STRUCTURE:

BRANCHES:

`master` BRANCH:

The master branch is the current edge of development.

`X.X` BRANCH:

The X.X branch is the last stable branch. It will used for tarballs.

MERGE REQUESTS:

If you want to merge your branch with the trunk, join the team.

Please base all Merge requests off the `master` branch. Merges to `X.X` only occur through the `master` branch.

PROBLEM REPORTING:

Bugs should be reported to bugs.launchpad.net/hoe-manns. You will need to create an account for yourself.