Changes

no edit summary
Line 1: Line 1:  +
Full release process is today done automatically and documented on page [[FAQ_Release_process]]
 +
 +
This page is a draft for evolution requets.
 +
 +
 
= Dolibarr release process =
 
= Dolibarr release process =
 
   
 
   
Line 18: Line 23:  
   
 
   
 
''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''
 
   
 
   
 
* Zipped archive
 
* Zipped archive
 
   
 
   
 
RD: ''I'd build it from the tarball''
 
RD: ''I'd build it from the tarball''
+
 
 
=== Distribution packages ===
 
=== Distribution packages ===
 
   
 
   
Line 90: Line 97:  
* 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 ==
Line 204: Line 219:  
* 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 ==