ReleaseProcess - Revision history

Eldy at 08:01, 28 October 2016

2016-10-28T08:01:04Z

← Older revision		Revision as of 08:01, 28 October 2016
Line 1:		Line 1:
			Full release process is today done automatically and documented on page [[FAQ_Release_process]]

	This page ~~seems to be deprecated~~. ~~Full release process is today done automatically and documented on page~~		This page is a draft for evolution requets.
	~~[[FAQ_Release_process]]~~

Eldy at 07:59, 28 October 2016

2016-10-28T07:59:57Z

← Older revision		Revision as of 07:59, 28 October 2016
Line 1:		Line 1:

			This page seems to be deprecated. Full release process is today done automatically and documented on page
			[[FAQ_Release_process]]


	= Dolibarr release process =		= Dolibarr release process =

Rdoursenaud: Add nice to have releases

2016-10-19T14:20:58Z

Add nice to have releases

← Older revision		Revision as of 14:20, 19 October 2016
Line 92:		Line 92:
	* Virtualmin installer		* Virtualmin installer
	* Proxmox Appliance		* Proxmox Appliance

			== Nice to have ==

			RD: ''Releases that don't exist just yet but would help reaching farther IMHO''

			* GitHub releases

			* Packagist.org (Compser)

	== Tentative process ==		== Tentative process ==

Saxa: /* Archives */

2014-12-23T18:05:49Z

Saxa: /* Archives */

2014-12-23T18:05:27Z

Eldy: /* RD */

2014-03-12T19:04:51Z

← Older revision		Revision as of 19:04, 12 March 2014
Line 204:		Line 204:
	* More projects are moving to tar.xz releases, shan't we join the boat?		* More projects are moving to tar.xz releases, shan't we join the boat?
	* Shouldn't we use native environments to build distribution packages and windows installer? Vagrant maintained virtual build and test machines would be neet.		* Shouldn't we use native environments to build distribution packages and windows installer? Vagrant maintained virtual build and test machines would be neet.
			LD: More then 80% of users prefer to use installer, and 60% of dowload are for wamp installer, so we must keep native distribution packages.
	* [https://aur.archlinux.org/packages/dolibarr Arch Linux package] could be adopted and made up to par with other distro's		* [https://aur.archlinux.org/packages/dolibarr Arch Linux package] could be adopted and made up to par with other distro's
	* Shouldn't we publish also on GitHub since it's one of our homes now? This can be fully automated with the [http://developer.github.com/v3/repos/releases/ API]		* Shouldn't we publish also on GitHub since it's one of our homes now? This can be fully automated with the [http://developer.github.com/v3/repos/releases/ API]
	* Is there other announcements to be made?		* Is there other announcements to be made?
	* Release script is in Perl now, I'd like to rewrite it with [http://www.phing.info Phing]. Any objections ?		* Release script is in Perl now, I'd like to rewrite it with [http://www.phing.info Phing]. Any objections ?
			LD: No, it would be better to have only php tools.

	== Misc. Notes ==		== Misc. Notes ==

Rdoursenaud: Make document status m

2014-01-10T13:44:57Z

Make document status m

← Older revision		Revision as of 13:44, 10 January 2014
Line 1:		Line 1:
	= Dolibarr release process =		= Dolibarr release process =

	This document is a draft ~~trying~~ to ~~understand~~ what ~~is going on~~ to release ~~dolibarr~~.		This document is a '''draft'''.

			The intention is to document what needs to be done to release Dolibarr.

	RD: ''I intend to use it as a base to revamp the whole releasing process.''		RD: ''I intend to use it as a base to revamp the whole releasing process.''

Rdoursenaud: Added prefix to comments

2014-01-10T13:39:58Z

Added prefix to comments

Show changes

Rdoursenaud: Création

2014-01-10T13:26:41Z

Création

New page

= Dolibarr release process =

This document is a draft trying to understand what is going on to release dolibarr.

''I intend to use it as a base to revamp the whole releasing process.''

== Officialy maintained ==

=== Descriptor ===

* [http://pad.asp-software.org Portable Application Description]

=== Archives ===

* Gziped tar archive

''Actually uses the .tgz extension, I'd prefer the more common .tar.gz''

* Zipped archive

''I'd build it from the tarball''

=== Distribution packages ===

''I'd make these from the release tarball.''

==== RPM ====

''Can't all of these be unified?''

* Generic
* Fedora

''RedHat?''

* Mandriva

''Is this really needed? I mean who still uses mandriva these days?''

* OpenSuse

==== DEB ====

* Debian

''Ubuntu?''

=== Installers ===

* Windows (DoliWamp, exe)

''This one is the most involved. We need a better spec of the process.''

== '''Not''' officially maintained ==

''Need volunteers?''

These packages are not officially maintained but are in the source tree. Maybe we'd want to have them work one day or another.

* [http://www.apsstandard.org APS]
* MacOS X installer (DoliMamp, dmg)
* [https://github.com/edumbill/doap/wiki DOAP]

''Is this even a package format?''

* Doxygen (Developer documentation)

''Again, not a package format, but this should certainly be published somewhere for each released version''

* Launchpad (https://launchpad.net/dolibarr)

''Ubuntu packages and build system?''

* Live CD

''Really? What for? Demos? Looks overkill''

* [https://build.opensuse.org/project/show/Application:ERP:Dolibarr OpenSuse build system]

''This one is pretty cool. Looks like we could leverage its capabilities to automate the builds of our Linux distribution packages.'' ''Credentials needed''

* Virtualmin installer
* Proxmox Appliance

== Tentative process ==

=== Early announcement ===

# Post to dolibarr-dev intention to package. Ask testers to test. Ask translators to update their translations. Fix release date allowing at least ''one'' week for people to do their tasks.

=== Building ===

# Update version numbers in source code, ChangeLog and PAD files
# Commit and Tag version

''Better be a [http://git-scm.com/book/en/Git-Basics-Tagging#Signed-Tags signed tag]''

<ol start="3" style="list-style-type: decimal;">
<li>Checkout tag to a test directory</li>
<li>Play unit tests</li>
<li>Play UI tests</li></ol>

If all is OK

<ol start="6" style="list-style-type: decimal;">
<li>Checkout tag to a build directory</li>
<li>Clean build directory (i.e. remove stuff that won't go into release. Includes devolopment tools, samples, test results, git repo itself, etc.)</li>
<li>Fix rights</li>
<li>TAR reference release</li></ol>

''We should also generate checksums''

''Add a GPG signature?''

<ol start="10" style="list-style-type: decimal;">
<li>ZIP release</li>
<li>RPM releases</li>
<li>DEB realease</li>
<li>Windows installer release</li></ol>

=== Testing ===

* ?

=== Pushing ===

# Tag to central repository

''Credentials needed. This won't get along with a pull request!''

<ol start="2" style="list-style-type: decimal;">
<li>Packages, Artifacts (Checksum(s), signature(s)…), ChangeLog and PAD files to dolibarr.org (/home/dolibarr/wwwroot/files)</li></ol>

''Credentials needed''

<ol start="3" style="list-style-type: decimal;">
<li>Packages to [http://sourceforge.net/projects/dolibarr/ Sourceforge.net]</li></ol>

''Credentials needed''

''Can be automated: [https://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download doc]''

=== Verifiing ===

* ?

''This is where checksums comes in handy''

=== Releasing ===

# Craft announcement message

''The message template should be in the repo''

<ol start="2" style="list-style-type: decimal;">
<li>Post announcement as a news on dolibarr.org</li></ol>

''Credentials needed''

<ol start="2" style="list-style-type: decimal;">
<li>Send announcement on Social Networks</li></ol>

* [https://plus.google.com/+DolibarrOrg Google+]
* [http://www.twitter.com/dolibarr Twitter]
* [http://www.facebook.com/dolibarr Facebook]

''Credentials needed''

''Should all be automated through their respective APIs''

<ol start="3" style="list-style-type: decimal;">
<li>Send announcement on Mailing lists</li></ol>

dolibarr-user, dolibarr-dev, dolibarr-foundation

<ol start="4" style="list-style-type: decimal;">
<li>Send announcement on Forum</li></ol>

''This should be a sticky in the appropriate category (which?)''

''Credentials needed''

== Misc. Questions ==

* More projects are moving to tar.xz releases, shan't we join the boat?
* Shouldn't we use native environments to build distribution packages and windows installer? Vagrant maintained virtual build and test machines would be neet.
* [https://aur.archlinux.org/packages/dolibarr Arch Linux package] could be adopted and made up to par with other distro's
* Shouldn't we publish also on GitHub since it's one of our homes now? This can be fully automated with the [http://developer.github.com/v3/repos/releases/ API]
* Is there other announcements to be made?
* Wiki!
* Doliforge (release number)!

''Credentials needed''

* Release script is in Perl now, I'd like to rewrite it with [http://www.phing.info Phing]. Any objections ?

== Misc. Notes ==

* Directory structure for resulting binaries should be :

<pre>.
├── generic
├── package_aps
├── package_debian-ubuntu
├── package_mac
├── package_rpm_generic
├── package_rpm_mandriva
├── package_rpm_opensuse
├── package_rpm_redhat-fedora
└── package_windows</pre>
* We need to define the versioning and naming conventions as well as the branching system

← Older revision		Revision as of 18:05, 23 December 2014
Line 18:		Line 18:

	''Actually uses the .tgz extension, I'd prefer the more common .tar.gz''		''Actually uses the .tgz extension, I'd prefer the more common .tar.gz''

	''SO: In my opinion it would be even better if we could use .tar.xz''		''SO: In my opinion it would be even better if we could use .tar.xz''