Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
D
dolibarr
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Container registry
Model registry
Analyze
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Software_Artifact_Infrastructure_Repository
dolibarr
Commits
99e2bfb0
Commit
99e2bfb0
authored
15 years ago
by
Laurent Destailleur
Browse files
Options
Downloads
Patches
Plain Diff
Update documentation
parent
1f11eac7
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
build/makepack-howto.txt
+40
-10
40 additions, 10 deletions
build/makepack-howto.txt
with
40 additions
and
10 deletions
build/makepack-howto.txt
+
40
−
10
View file @
99e2bfb0
***** Actions to do to release *****
----- Dolibarr Makepack How To -----
This documentation describe steps to build a BETA or RELREASE versions
of Dolibarr. There is a chapter for BETA version and a chapter vor
RELEASE version.
***** Actions to do a BETA *****
This files describe steps made by Dolibarr packaging team to make a
beta version of Dolibarr, step by step.
- Check all files are commited.
- Update version/info in / directory (README*.txt, ChangeLog...)
- Update version number in build/makepack-dolibarr.pl
- Update version number in build/exe/doliwamp/doliwamp.iss
- Update version number in htdocs/master.inc.php
- Update version number in htdocs/install/inc.php
- Commit all changes.
- Add a CVS Tag (DOLIBARR_x_y_BETA)
- If it's a new branch (Vx.y), create a branch (DOLIBARR_x_y_BRANCH).
- Build Dolibarr and DoliWamp with makepack-dolibarr.pl
- Check content of built packages.
- Move build files (tgz+exe+deb), ChangeLog and PAD/DOAP files into the
Dolibarr web site repository /home/dolibarr/wwwroot/files.
- Update and upload NLTechno web page with DoliWamp version.
- Add/Update entries on joomla web site www.dolibarr.org with links
to files http://www.dolibarr.org/files/XXX.
- Send mail on mailings-list
***** Actions to do a RELEASE *****
This files describe steps made by Dolibarr packaging team to make a
complete release of Dolibarr, step by step.
- Check all files are commited.
- Update
files in root
directory (README*.txt, ChangeLog...)
- Update
version/info in /
directory (README*.txt, ChangeLog...)
- Update version number in build/makepack-dolibarr.pl
- Update version number in build/doxygen/dolibarr-doxygen.doxyfile
- Update version number in build/exe/doliwamp/doliwamp.iss
...
...
@@ -12,19 +43,18 @@ complete release of Dolibarr, step by step.
- Update version number in htdocs/install/inc.php
- Update PAD and DOAP files.
- Commit all changes.
- Add a CVS Tag
- If it's a new branch (Vx.y), create a branch.
- Add a CVS Tag (DOLIBARR_x_y)
- Build Dolibarr and DoliWamp with makepack-dolibarr.pl
- Check content of built packages.
- Move build files (tgz+exe), ChangeLog and PAD/DOAP files into
Dolibarr
web site repository /home/dolibarr/wwwroot/files.
-
Move
links in directory "/home/dolibarr/wwwroot/files" on server to
point
to new files.
-
U
pload NLTechno web page with DoliWamp version.
- Move build files (tgz+exe
+deb
), ChangeLog and PAD/DOAP files into
the
Dolibarr
web site repository /home/dolibarr/wwwroot/files.
-
Edit symbolic
links in directory "/home/dolibarr/wwwroot/files" on server to
point
to new files.
-
Pudate and u
pload NLTechno web page with DoliWamp version.
- Upload files dolibarr.*.tgz and doliwamp.*.exe on sourceforge.
- Update entries on joomla web site www.dolibarr.org with new sourceforge link.
-
Add/
Update entries on joomla web site www.dolibarr.org with new sourceforge link.
- Send mail on mailings-list
- Send news on OpenSource web sites (if major beta or release)
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment