forked from yapbam/yapbam
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdeliveryProcess.html
75 lines (75 loc) · 3.79 KB
/
deliveryProcess.html
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
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=windows-1252" http-equiv="content-type">
<title>Yapbam delivery process</title>
<style type="text/css">
.variable {
font-style: italic;
text-decoration: underline;
}
</style></head>
<body>
<h1>Yapbam delivery process</h1>
<ol>
<li>Get the translations from Crowdin.<br>
First check on <a href="https://crowdin.com/project/yapbam">Crowdin</a>
that no translation occurred since last build (if so build the project).<br>
Launch the com.fathzer.localization.crowdin.GetTranslationsCmd in
jlocal-tools project with arguments project=yapbam key=<span style="font-style: italic;">theyapbamkey</span>
lng=fr,pt-BR:pt,de,en:,zh-TW:zh,tr,nl,ru,ro,pl,hu,es-ES:es,it,ar,ja,el where=<span style="font-style: italic;">workspaceRoot</span><br>
Then, check whether YapbamCommons translations has changed. In such a
case, update the artifact.<br>
<span style="font-weight: bold; text-decoration: underline;">Be aware of
changes in Yapbam web resources</span>. Due to a Crowdin bug, ':' and
'=' characters are preceded by a escape '\' character. Note also that
the French and English versions of 'TranslationNeeded.supported' key is
not the one stored in Crowdin.</li>
<li>Set the version number in the pom.xml file<span class="variable"></span></li>
<li>Run maven clean package on pom.xml => That creates a ready to
deploy zip file in the project directory.<br>
<span class="variable"></span></li>
<li>Create the windows installer with NSIS.<br>
select the "Installer based on a zip file" option and enter
"$EXEDIR\Yapbam" as default folder.</li>
<li>Run net.yapbam.deployment.YapbamDeployer in project YapbamDeployment (Be aware to set the
right versions in the program fields).<br>
Wait for it completes (it is long as this class upload Yapbam to
sourceForge).<br>
<span style="font-weight: bold; text-decoration: underline;">Copy the
release notes on the official site</span> (the deployer deploys only
on sourceforge)</li>
<li>Test that the autoupdate is ok with a copy of the previous version of
yapbam. Also test that the archives on sourceforge are ok ...
sometimes, upload results in a partial file.</li>
<li>In the sourceforge file browser, give the linux, BSD, etc...
attributes (or windows) to the new uploaded files.</li>
<li>Commit pending changes to svn repository.</li>
<li>Post a comment on twitter.</li>
<li>Post replies on opened bug report or feature requests.</li>
<li>Mise à jour du référencement par anshare (www.anshare.org)</li>
<ol>
<li>Mettre à jour la fiche logiciel :</li>
<ol>
<li>Mettre un lien vers cet .exe (les liens de téléchargement de
sourceforge sont interdits) :
http://www.yapbam.net/directDownload/yapbam-<span style="font-style: italic;">version</span>.exe.</li>
<li>Supprimer Linux dans les OS cible (l'auteur du site ne connait pas
le principe de Write Once Run Everywhere, donc on n'a droit qu'à un
seul OS).</li>
</ol>
</ol>
</ol>
<br>
<h2>A way to carefully test the auto update</h2>
<ol>
<li>In net.yapbam.update.VersionManager#getUpdateURL, change the
updateinfo URL to a local file and put a fake version number in
net.yapbam.update.version.txt</li>
<li>In this local file, copy the following lines ouputed by
srcTests/net.yapbam.update.GetHashAndSize</li>
<li>Launch this modified version of yapbam.</li>
<li>Try to update.</li>
</ol>
</body>
</html>