> Announcement: FAQ for curators and topic starters
FAQ for curators and topic starters


Version number, update date, builds, versions and versions
  • The header of the header (under the name) indicates the number of the stable version only.
  • The update date of the header also changes only when adding a stable version. It does not matter which option (GP, premium, mod, etc.) is added, the main thing is that it is a stable version. If another option is added, but with the number of an existing version, the date does not change.
  • When adding a new build of the same version of the program, the update date of the header does not change (except for individual programs, where the build number is in the version number). The build number (if available) is not written in the title, only in the Download block. The new build in the Download block replaces the last stable one and, if obsolete, is transferred to previous versions.
  • If a program has different versions of versions (GP, Premium, Mod, Rus Mod, etc.), the Download section should always contain the latest versions of each existing version. That is, if the latest version of the mod lags behind the current regular version, but the newer mod is not laid out, then it remains in the main block.
  • If the developer implements different apk-files for different architectures (arm, arm64, x86), then in the Download block there should be links to the latest versions of each architecture. The version number in the header of the header changes to the older version, no matter for what architecture it is laid out.
  • Backup for Titanium Backup is also considered a release.
  • Links to all previous versions should be located in the same spoiler in the topic header (or in a separate post, but with a link to it in the header).

Adding non-stable versions (Beta, Release Canditate (RC), Debug)
The update date of the header and the version number in the header do NOT change.
Beta / RC / Debugare added in parallel with the last stable in the Download block.
If we add a new oneBeta / RC / Debugor stable with the number above, the previous oneBeta / RC / Debugremove from the cap.

Change the required version of Android
If there was a change in the required version of Android, then this should be reflected in the topic header. The most logical thing in the Download block is to leave a link to the latest version with other requirements with their indication.
Example
Requirements: 5.0+
....
Download
Version: 2.0 ...
Version: 1.2 (4.0+) ...


Release Rules
Posts with violations of the rules of release of new versions can not be added to the header.
For TS'ov
You can either click the Complaint and report a violation of the release rules, or talk to the release in QMS (private messaging system).
For curators
Formally, a separate post can hang the tag of the following content, highlighting the item that was not executed:
Tag
Rules section and FAQ on creating and updating topics
Software update
Release a new (or translated) version
To properly lay out a new (or translated) version of the program, you must perform the following steps:
  • Be sure to upload the file (apk, exe, zip) to the post
  • clearly indicate the version of the program
  • be sure to add a list of changes
  • publish the post and report it to the moderators on the button "complaint"

[cur] [b] [url = "//savagemessiahzine.com/forum/index.php?act=announce&f=212&st=250""Rules of the section and FAQ on creating and updating topics [/ url] [/ b]
[color = blue] [b] Software Update [/ b] [/ color]
Release a new (or translated) version
To properly lay out a new (or translated) version of the program, you must perform the following steps:
[list] [*] necessarily upload the file (apk, exe, zip) to the post
[*] clearly indicate the version of the program
[*] be sure to add a list of changes
[*] publish the post and report it to the moderators by the button "complaint" [/ list] [/ cur]

Or you can talk to the releaser on this topic in QMS.
If he does not want or cannot edit, then you can either leave everything as it is without adding a post to the header, or independently align the post with the rules, if you are sure of the information being added, by taking a screenshot of the original version of the message.
If the post is edited, it should be added to the header, and the tag (if any) should be deleted. If the violation of the rules remains, then after the release of the next version of the post with the wrong release and tag (if any) also should be removed.

Links to the site (even if the developer himself) are not suitable as a changelog. The “List of changes unknown” option is valid.
If another option is laid out (premium, mod, etc.) of an already existing version, then the list of changes is not mandatory, since it should have already been specified in the existing version.

Other
As noted in the section rules, links to groups on social networks and various instant messengers are prohibited for publication. An exception can be made only for those clients of social data. networks and instant messengers and only in agreement with the section moderators.
To curators - if you see similar links in posts of users, then either delete the post if it is not useful, or edit it (by taking a screenshot of the original), removing links if the post is useful (release, mod, instruction, etc.) TS'am - Click on the complaint.


 mobile version Now: 05/18/19, 00:29