Release policy

Open
#2,235 12 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Domain
release

Research direction

Read CONTRIBUTING.md at the linked Gradle section first; no source file, test, or code entry point is named. The stated completion condition is a release request comment containing the reason and days since the last release, but no implementation task is defined.

Written by the indexing model from the issue text.

Description

enhancement

We have JitPack setup, so you can grab any commit you want at any time, see these instructions.

The whole point of Spotless is that formatting should not matter. If your formatting plugin is creating "new release" notifications every week then formatting is taking up more time in the ecosystem than it should.

  • if you want a release
  • and it has been more than 30 days since the last release
  • comment here in this issue with
    • why you want a release
    • the number of days since the last release
  • and that will kick my butt and I'll do the release

Please don't spam other issues with comments related to "release please!". Keep that here.

Dominant language
Java
Stars
5.7k
Forks
560
Avg merge
1d 13h
Merged PRs (30d)
43

Contributor guide

Open the contributing guide

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 diffplug/spotless

All issues in diffplug/spotless

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.