| ... | ... | @@ -127,6 +127,8 @@ This stage is essentially the completion of this project. However, we expect tha |
|
|
|
* q. Complete alternative data routes using MESH-like networking, when cellular services have been interrupted
|
|
|
|
* r. Complete advanced statistical analysis of fake BTS towers
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
##### Versioning
|
|
|
|
|
|
|
|
* When changing code on `development` branch **(any developer)**:
|
| ... | ... | @@ -137,3 +139,16 @@ This stage is essentially the completion of this project. However, we expect tha |
|
|
|
|
|
|
|
android:versionCode="**25**" -> android:versionCode="**26**" -> android:versionCode="**27**"...
|
|
|
|
When releasing, we're also going to count upwards: 0.1.**25**-alpha -> 0.1.**26**-alpha...
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
### BugFixChallenge - win a SURPISE!
|
|
|
|
|
|
|
|
:sparkles: Welcome to the cool stuff! :sparkles: Here are the rules:
|
|
|
|
|
|
|
|
1. `#BugFixChallenge` takes place every THURSDAY before release.
|
|
|
|
2. Read our [development note](https://github.com/SecUpwN/Android-IMSI-Catcher-Detector/blob/development/CONTRIBUTING.md#developing). Then pick any [Issue](https://github.com/SecUpwN/Android-IMSI-Catcher-Detector/issues) you like.
|
|
|
|
3. Introduce yourself in that Issue and "save it for yourself".
|
|
|
|
4. Submit a pull request for your Issue, preferably only one.
|
|
|
|
5. If the Issue is really fixed and closed, we will contact you.
|
|
|
|
6. The person with the most fixes will also be thanked via [our Twitter](https://twitter.com/AIMSICD). |
|
|
\ No newline at end of file |
