summaryrefslogtreecommitdiff
path: root/RELEASE.md
blob: a1f67c0443a1c8693c98f742dbdddcc1d77efd8b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
# PHP Malware Finder release documentation

## What should I do before releasing ?

Thou shalt test your modifications. If everything goes fine, you should see this
message:
```
$ ./tests.sh 
[+] Congratz, the 54 tests succeeded!
```

Otherwise, your modifications introduced a regression, check how to fix this,
then test again until all tests pass.

## OK, it's done, how do I release my new PMF version now ?

First, make sure enough modifications have been made to warrant a new release.
Since PMF provides its own debian package files, you can build a package,
hence need to modify the changelog file to add an entry in the debian/changelog
file:

```
nbs-phpmalwarefinder (X.Y.Z-T~deb##version+nbsYYYMMDD) distrib; urgency=XXX

  * new feature
  * bug fix
  * moar documentation

 -- yournick <your@email.com>  `date -R`
```

Then you can commit on our git repository:
```
$ git commit -am "my changes"
$ git tag X.Y.Z
$ git push
```