Collection of License badges for your Project's README file.
This list includes the most common open source and open data licenses.
Easily copy and paste the code under the badges into your Markdown files.
Translations: (No guarantee that the translations are up-to-date)
| /** | |
| * Author: Ian Gallagher <igallagher@securityinnovation.com> | |
| * | |
| * This code utilizes jBCrypt, which you need installed to use. | |
| * jBCrypt: http://www.mindrot.org/projects/jBCrypt/ | |
| */ | |
| public class Password { | |
| // Define the BCrypt workload to use when generating password hashes. 10-31 is a valid value. | |
| private static int workload = 12; |
| aardvark | |
| aardwolf | |
| Aaronite | |
| abaction | |
| abaculus | |
| abaissed | |
| abampere | |
| Abarambo | |
| abasedly | |
| abatable |
| Develop Current Task | QA Current Task | QA Older Task | Release Current Task | Release Older Task | Release Even Older Task | On Time | |
|---|---|---|---|---|---|---|---|
| T | T | T | T | T | T | T | |
| T | T | T | T | T | F | F | |
| T | T | T | T | F | T | F | |
| T | T | T | T | F | F | F | |
| T | T | T | F | T | T | F | |
| T | T | T | F | T | F | F | |
| T | T | T | F | F | T | F | |
| T | T | T | F | F | F | F | |
| T | T | F | T | T | T | F |
| Develop | QA | Release | On Time | |
|---|---|---|---|---|
| T | T | T | T | |
| T | T | F | F | |
| T | F | T | F | |
| T | F | F | F | |
| F | T | T | F | |
| F | T | F | F | |
| F | F | T | F | |
| F | F | F | F |
These rules are adopted from the AngularJS commit conventions.
In the last few yers, the number of programmers concerned about writting structured commit messages had dramatically grown. As exposed by Tim Pope in article readable commit messages are easy to follow when looking through the project history. Moreover the AngularJS contributing guides introduced conventions that can be used by automation tools to automatically generate useful documentation, or by developpers during debbuging process.
This document borrow some concepts, conventions and even text mainly from these two sources, extending them in order to provide a sensible guideline for writing commit messages.
When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
Please note we have a code of conduct, please follow it in all your interactions with the project.
Imagine that you are versioning your sourcecode in git and building your code via maven. You need to make releases before deploying to production regularly. What should be the strategy we need to follow for releasing?
I've used maven-release-plugin for years to make releases. It worked perfectly with maven and svn, but we started to face problems when we migrated our code to git and to make releases on git.
After checking the literature, we decided to use JGit-Flow which is a maven plugin based on and is a replacement for the maven-release-plugin enabling support for git-flow style releases via maven.
I do not want to explain the details much because there are many great posts explaining all.