常见问题-发布流程 - Revision history

ShengGang: /* 打包最终版本 */

2023-10-13T03:50:51Z

打包最终版本

← Older revision		Revision as of 03:50, 13 October 2023
Line 75:		Line 75:
	*从此刻开始，一个新的周期可以开始了。从这个版本的源代码开始一个新的开发期。		*从此刻开始，一个新的周期可以开始了。从这个版本的源代码开始一个新的开发期。

	~~Then a~~ Dolibarr Yoda ~~add 1 page (one page per version) onto the~~ https://wiki.dolibarr.org ~~to describe content of new version. This is the Release announcement. You can look at the page~~ [[:Category:RoadMap]] ~~for list of past announcements.~~		然后 Dolibarr Yoda 将在 https://wiki.dolibarr.org 上新增一个页面（每个版本一个页面），用于描述新版本的内容。这是版本发布公告。您可以在 [[:Category:RoadMap]] 页面上查看过去的公告清单。

	At any time, from the menu '''System Tools / About Dolibarr / Check integrity''', an admin user can check and validate integrity of its installed version compared to official reference. The tool calculate signature of each file and compare it with official signature. All removed and modified files are reported.		在任何时候，通过菜单“主页-管理工具-关于Dolibarr-文件集完整性检查”，管理员用户都可以检查并验证其安装版本相比与官方参考版本的完整性。该工具计算每个文件的签名，并将其与官方签名进行比较。将报告所有被删除和被修改的文件。

	~~At any time, a developer can, from Github and using the~~ '''Tag''' ~~created at first step of release process, get all files of any stable version.~~		在任何时候，开发人员都可以在Github上使用发布流程第一步创建的 '''Tag''' 来获取任何稳定版本的所有文件。

ShengGang: /* Continuous interation */

2023-10-13T03:36:33Z

Continuous interation

← Older revision		Revision as of 03:36, 13 October 2023
Line 18:		Line 18:
	以下这是对这三个时期的描述。		以下这是对这三个时期的描述。

	=开发=		=开发期=

	==开发==		==开发==
Line 28:		Line 28:
	有关如何执行这些操作的详细信息，请参见 [[FAQ_Get,update_GIT_project_sources\|FAQ Get or update project with GIT]] 。		有关如何执行这些操作的详细信息，请参见 [[FAQ_Get,update_GIT_project_sources\|FAQ Get or update project with GIT]] 。

	==~~Continuous interation~~==		==持续交流==

	~~Each time a new request to include a change is submitted, Continuous Integration Tests are done before the change is validated.~~		每次提交包含变更的新请求时，都会在验证变更之前完成持续集成测试。

	~~Continuous integration Test are included into official sources into directory~~ tests~~. They are run on the Travis platform and can be analyzed here:~~ https://travis-ci.org/Dolibarr/dolibarr/		持续集成测试被包含在目录tests下的官方源代码中。它们在Travis平台上运行，可以在此处进行分析： https://travis-ci.org/Dolibarr/dolibarr/

	~~If a test fails, it will not be validated (see next step).~~		如果测试失败，将不会对其进行验证（请参阅下一步）。

	==~~Validation of new changes~~==		==验证新变更==

	~~Only people with the grade~~ '''Dolibarr Yoda''' ~~can accept to include changes into official development sources. Permissions for this are granted on GitHub~~		只有'''Dolibarr Yoda'''级别的人才能接收并将变更纳入官方开发源代码。此权限在GitHub上授予

	~~See~~ [[Dolibarr_Project#Developers_roles\|Dolibarr roles]] ~~for the list of people with this grade.~~		有关拥有此级别的人员列表，请参阅 [[Dolibarr_Project#Developers_roles\|Dolibarr roles]] 。

	=~~Beta period~~=		=测试期=

	~~When enough changes are included into version, and according to planning, the Dolibarr Yoda decide to start the beta.~~		当版本中包含了足够多的变更后，根据计划，由Dolibarr Yoda决定开始测试。
	~~Starting from this point, no new features are added.~~

	~~See page [[:Category:RoadMap]] for standard planning of new versions and rules that define what kind of code can be modified or not during a beta period.~~		从这一刻开始，不会再添加任何新功能。

			请参见页面 [[:Category:RoadMap]] ，了解新版本和规则的标准规划，这些版本和规则定义了在测试期间可以修改或不可以修改的代码类型。

	~~Generating the~~ packages ~~is done using the packaging tool~~ '''makepack_dolibarr.pl'''~~. See next chapter for detailed operation done by this tool.~~		生成 packages 是使用打包工具 '''makepack_dolibarr.pl''' 完成的。有关该工具的详细操作，请参阅下一章。

	=~~The packaging of final releases~~=		=打包最终版本=
	~~When beta period end (no more serious bugs are reported and opened), the Dolibarr Yoda decide to start the freeze of final version. The name of the version is define to a value X~~.Y.Z.		当测试期结束（没有严重bugs的报告和打开），由Dolibarr Yoda决定开始冻结最终版本。版本的名称定义为值X.Y.Z。

	~~Note: Only a Dolibarr Yoda can make this process.~~		注意：只有Dolibarr Yoda才能执行此操作。

	*~~Firstly, final Unit Tests are run. If 1 test is wrong, process is stopped here and go back to beta phase~~.		*首先，运行最后的单元测试。若发现有1个测试错误，停止后续操作并返回测试阶段。 <br />所有测试都正常后，将使用打包工具 '''makepack_dolibarr.pl''' 自动执行以下步骤：

			*该工具生成（或建议生成） '''ChangeLog''' 文件。此文件是与源代码一起被提交的。
	~~Once all tests are ok, the following steps are done automatically using the packaging tool '''makepack_dolibarr.pl''' :~~		*该工具生成文件'''filelist-X.Y.Z.xml'''，其中包含具有MD5签名和版本值的版本文件清单。此文件是与源代码一起被提交的。
			*该工具在官方源代码存储库的所有文件上添加一个'''Tag'''，该'''Tag'''是版本的名称（即X.Y.Z）。因此，从现在开始，专用版本的所有文件都是已知的，并且不会再更改。
	*~~The tool generate (or suggest the command to generate) the~~ '''ChangeLog''' ~~file. This file is commited with sources.~~		*该工具构建所有的'''官方分发包'''。此类包的内容和签名文件的内容相匹配，因为签名文件是在同一过程中生成的。其构建了以下程序包：
	*~~The tool generates the file~~ '''filelist-X.Y.Z.xml''' ~~than contains the list of files of the version with a MD5 signature and value of version. This file is commited with sources.~~		**Package '''.zip''' (主包）
	*~~The tool add a~~ '''Tag''' ~~that is the name of version (so X~~.Y.~~Z) on all files of the official source repository. So starting from now, all files for the dedicated version are known and won't change anymore.~~
	*~~The tool build all~~ '''~~official distribution packages~~'''~~. Content of such packages match the content of the signature file since it is build during same process. The following packages are built:~~
	**Package '''.zip''' (~~the main package)~~
	**Package '''.tgz'''		**Package '''.tgz'''
	**~~Autoinstaller~~ Doliwamp '''.exe'''		**自动安装程序 Doliwamp '''.exe'''
	**~~Autoinstaller for~~ Debian/Ubuntu DoliDeb '''.deb'''		**基于 Debian/Ubuntu 平台的自动安装程序 DoliDeb '''.deb'''
	**~~Autoinstaller for Redhat, linuxmint, mandriva~~ DoliRpm '''.rpm'''		**基于 Redhat、linuxmint、mandriva 平台的自动安装程序 DoliRpm '''.rpm'''
	*~~The tool upload the generated signature file~~ '''filelist-X.Y.Z.xml''' ~~on the official Dolibarr server. This file can be read by any installed application to check the integrity of the version (even one byte modified will change the signature).~~		*该工具将生成的签名文件 '''filelist-X.Y.Z.xml''' 上传到官方的Dolibarr服务器上。任何已安装的应用程序都可以读取此文件，以检查版本的完整性（即使修改了一个字节也会使签名改变）。
	*~~The tool upload the generated packaged into the~~ '''~~official Dolibarr archive server~~''' ~~to have them archived also in a binary form. This archives can be read from page~~ https://www.dolibarr.org/files/stable/		*该工具将生成的包上传到'''官方的Dolibarr存档服务器'''，以二进制形式进行存档。读取该存档的页面是<nowiki/>https://www.dolibarr.org/files/stable/
	*~~The tool upload the generated packaged into the '''mirror archive servers''' hosted at~~ https://www.sourceforge.net~~. This is a mirror hosting, official references remain the Dolibarr archive area and are hosted by the Dolibarr team so at~~ https://www.dolibarr.org/files/stable/.		*该工具将生成的包上传到托管在 https://www.sourceforge.net 的'''镜像存档服务器'''中。这是一个镜像托管，官方参考资料仍然保留在Dolibarr存档区，由Dolibarr团队托管，位于 https://www.dolibarr.org/files/stable/.
	*~~The release is also created on~~ https://GitHub.com/Dolibarr/dolibarr		*该版本也被创建到 https://GitHub.com/Dolibarr/dolibarr
	*~~Then people of the Dolibarr community send announcements on different channels (www~~.dolibarr.~~org, forums, social networks...).~~		*然后，Dolibarr社区的人们在不同的渠道（www.dolibarr.org、论坛、社交网络…）上发布公告。
	*~~Starting from now, a new cycle can start. A new development period start from sources of the version.~~		*从此刻开始，一个新的周期可以开始了。从这个版本的源代码开始一个新的开发期。

	Then a Dolibarr Yoda add 1 page (one page per version) onto the https://wiki.dolibarr.org to describe content of new version. This is the Release announcement. You can look at the page [[:Category:RoadMap]] for list of past announcements.		Then a Dolibarr Yoda add 1 page (one page per version) onto the https://wiki.dolibarr.org to describe content of new version. This is the Release announcement. You can look at the page [[:Category:RoadMap]] for list of past announcements.

ShengGang: /* Introduction */

2023-10-13T02:41:35Z

Introduction

← Older revision		Revision as of 02:41, 13 October 2023
Line 9:		Line 9:
	[[Category:RoadMap]]		[[Category:RoadMap]]

	= ~~Introduction~~=		=简介=
	~~This page describe what is the build and release process of a new stable version of Dolibarr~~ ERP ~~CRM (manufacturing process or chaine de fabrication in french).~~		本页描述了Dolibarr ERP CRM（法语中的制造流程或供应链）的最新稳定版本的构建与发布流程。

	~~A new version is build following different steps:~~		按照不同的时期构建新版本：

	'''~~A development period~~ -> ~~A freeze~~ / ~~beta period~~ -> ~~A final stable version~~''' ~~(See page~~ [[:Category:RoadMap]] ~~for definition of a Freeze / Beta version)~~		'''开发期 -> 冻结/测试期 -> 最终稳定版本''' （有关冻结/测试版本的定义参见页面 [[:Category:RoadMap]] ）

	~~This is description of the 3 steps.~~		以下这是对这三个时期的描述。

	= ~~Development~~ =		=开发=

	== ~~Development~~ ==		==开发==

	~~First step is development of software. Sources can be download from~~ GitHub at https://github.com/Dolibarr/dolibarr		第一步是软件开发。可以从 GitHub 下载源代码，GitHub网址为 https://github.com/Dolibarr/dolibarr

	~~Any developer can download sources and work on his side using~~ git ~~and submit a request to ask to include his changes to the official sources.~~		任何开发者都可以下载源代码和使用 git 为自己工作，并可以提交请求以要求将自己的变更包含在官方源代码中。

	~~See the~~ [[FAQ_Get,update_GIT_project_sources\|FAQ Get or update project with GIT]] ~~for more information on how to do this.~~		有关如何执行这些操作的详细信息，请参见 [[FAQ_Get,update_GIT_project_sources\|FAQ Get or update project with GIT]] 。

	== Continuous interation ==		==Continuous interation==

	Each time a new request to include a change is submitted, Continuous Integration Tests are done before the change is validated.		Each time a new request to include a change is submitted, Continuous Integration Tests are done before the change is validated.
Line 36:		Line 36:
	If a test fails, it will not be validated (see next step).		If a test fails, it will not be validated (see next step).

	== Validation of new changes ==		==Validation of new changes==

	Only people with the grade '''Dolibarr Yoda''' can accept to include changes into official development sources. Permissions for this are granted on GitHub		Only people with the grade '''Dolibarr Yoda''' can accept to include changes into official development sources. Permissions for this are granted on GitHub
Line 42:		Line 42:
	See [[Dolibarr_Project#Developers_roles\|Dolibarr roles]] for the list of people with this grade.		See [[Dolibarr_Project#Developers_roles\|Dolibarr roles]] for the list of people with this grade.

	= Beta period =		=Beta period=

	When enough changes are included into version, and according to planning, the Dolibarr Yoda decide to start the beta.		When enough changes are included into version, and according to planning, the Dolibarr Yoda decide to start the beta.
Line 52:		Line 52:
	Generating the packages is done using the packaging tool '''makepack_dolibarr.pl'''. See next chapter for detailed operation done by this tool.		Generating the packages is done using the packaging tool '''makepack_dolibarr.pl'''. See next chapter for detailed operation done by this tool.

	= The packaging of final releases =		=The packaging of final releases=
	When beta period end (no more serious bugs are reported and opened), the Dolibarr Yoda decide to start the freeze of final version. The name of the version is define to a value X.Y.Z.		When beta period end (no more serious bugs are reported and opened), the Dolibarr Yoda decide to start the freeze of final version. The name of the version is define to a value X.Y.Z.

	Note: Only a Dolibarr Yoda can make this process.		Note: Only a Dolibarr Yoda can make this process.

	* Firstly, final Unit Tests are run. If 1 test is wrong, process is stopped here and go back to beta phase.		*Firstly, final Unit Tests are run. If 1 test is wrong, process is stopped here and go back to beta phase.


	Once all tests are ok, the following steps are done automatically using the packaging tool '''makepack_dolibarr.pl''' :		Once all tests are ok, the following steps are done automatically using the packaging tool '''makepack_dolibarr.pl''' :

	* The tool generate (or suggest the command to generate) the '''ChangeLog''' file. This file is commited with sources.		*The tool generate (or suggest the command to generate) the '''ChangeLog''' file. This file is commited with sources.
	* The tool generates the file '''filelist-X.Y.Z.xml''' than contains the list of files of the version with a MD5 signature and value of version. This file is commited with sources.		*The tool generates the file '''filelist-X.Y.Z.xml''' than contains the list of files of the version with a MD5 signature and value of version. This file is commited with sources.
	* The tool add a '''Tag''' that is the name of version (so X.Y.Z) on all files of the official source repository. So starting from now, all files for the dedicated version are known and won't change anymore.		*The tool add a '''Tag''' that is the name of version (so X.Y.Z) on all files of the official source repository. So starting from now, all files for the dedicated version are known and won't change anymore.
	* The tool build all '''official distribution packages'''. Content of such packages match the content of the signature file since it is build during same process. The following packages are built:		*The tool build all '''official distribution packages'''. Content of such packages match the content of the signature file since it is build during same process. The following packages are built:
	** Package '''.zip''' (the main package)		**Package '''.zip''' (the main package)
	** Package '''.tgz'''		**Package '''.tgz'''
	** Autoinstaller Doliwamp '''.exe'''		**Autoinstaller Doliwamp '''.exe'''
	** Autoinstaller for Debian/Ubuntu DoliDeb '''.deb'''		**Autoinstaller for Debian/Ubuntu DoliDeb '''.deb'''
	** Autoinstaller for Redhat, linuxmint, mandriva DoliRpm '''.rpm'''		**Autoinstaller for Redhat, linuxmint, mandriva DoliRpm '''.rpm'''
	* The tool upload the generated signature file '''filelist-X.Y.Z.xml''' on the official Dolibarr server. This file can be read by any installed application to check the integrity of the version (even one byte modified will change the signature).		*The tool upload the generated signature file '''filelist-X.Y.Z.xml''' on the official Dolibarr server. This file can be read by any installed application to check the integrity of the version (even one byte modified will change the signature).
	* The tool upload the generated packaged into the '''official Dolibarr archive server''' to have them archived also in a binary form. This archives can be read from page https://www.dolibarr.org/files/stable/		*The tool upload the generated packaged into the '''official Dolibarr archive server''' to have them archived also in a binary form. This archives can be read from page https://www.dolibarr.org/files/stable/
	* The tool upload the generated packaged into the '''mirror archive servers''' hosted at https://www.sourceforge.net. This is a mirror hosting, official references remain the Dolibarr archive area and are hosted by the Dolibarr team so at https://www.dolibarr.org/files/stable/.		*The tool upload the generated packaged into the '''mirror archive servers''' hosted at https://www.sourceforge.net. This is a mirror hosting, official references remain the Dolibarr archive area and are hosted by the Dolibarr team so at https://www.dolibarr.org/files/stable/.
	* The release is also created on https://GitHub.com/Dolibarr/dolibarr		*The release is also created on https://GitHub.com/Dolibarr/dolibarr
	* Then people of the Dolibarr community send announcements on different channels (www.dolibarr.org, forums, social networks...).		*Then people of the Dolibarr community send announcements on different channels (www.dolibarr.org, forums, social networks...).
	* Starting from now, a new cycle can start. A new development period start from sources of the version.		*Starting from now, a new cycle can start. A new development period start from sources of the version.

	Then a Dolibarr Yoda add 1 page (one page per version) onto the https://wiki.dolibarr.org to describe content of new version. This is the Release announcement. You can look at the page [[:Category:RoadMap]] for list of past announcements.		Then a Dolibarr Yoda add 1 page (one page per version) onto the https://wiki.dolibarr.org to describe content of new version. This is the Release announcement. You can look at the page [[:Category:RoadMap]] for list of past announcements.

PolyglotBot: Adding interlang links (links to translated versions of this page in other languages) triggered by origin English page "FAQ_Release_process" update.

2023-10-13T02:25:40Z

Adding interlang links (links to translated versions of this page in other languages) triggered by origin English page "FAQ_Release_process" update.

← Older revision		Revision as of 02:25, 13 October 2023
Line 1:		Line 1:
			<!-- BEGIN interlang links -->
			<!-- Do NOT edit this section
			Links below are automatically managed by PolyglotBot
			You can edit links on the English source page : FAQ_Release_process -->
			[[en:FAQ_Release_process]]
			<!-- END interlang links -->

	[[Category:FAQ ZH]]		[[Category:FAQ ZH]]
	[[Category:RoadMap]]		[[Category:RoadMap]]

ShengGang: initialization

2023-10-13T02:24:12Z

initialization

New page

[[Category:FAQ ZH]]
[[Category:RoadMap]]

= Introduction=
This page describe what is the build and release process of a new stable version of Dolibarr ERP CRM (manufacturing process or chaine de fabrication in french).

A new version is build following different steps:

'''A development period -> A freeze / beta period -> A final stable version''' (See page [[:Category:RoadMap]] for definition of a Freeze / Beta version)

This is description of the 3 steps.

= Development =

== Development ==

First step is development of software. Sources can be download from GitHub at https://github.com/Dolibarr/dolibarr

Any developer can download sources and work on his side using git and submit a request to ask to include his changes to the official sources.

See the [[FAQ_Get,update_GIT_project_sources|FAQ Get or update project with GIT]] for more information on how to do this.

== Continuous interation ==

Each time a new request to include a change is submitted, Continuous Integration Tests are done before the change is validated.

Continuous integration Test are included into official sources into directory *tests*. They are run on the Travis platform and can be analyzed here: https://travis-ci.org/Dolibarr/dolibarr/

If a test fails, it will not be validated (see next step).

== Validation of new changes ==

Only people with the grade '''Dolibarr Yoda''' can accept to include changes into official development sources. Permissions for this are granted on GitHub

See [[Dolibarr_Project#Developers_roles|Dolibarr roles]] for the list of people with this grade.

= Beta period =

When enough changes are included into version, and according to planning, the Dolibarr Yoda decide to start the beta.
Starting from this point, no new features are added.

See page [[:Category:RoadMap]] for standard planning of new versions and rules that define what kind of code can be modified or not during a beta period.

Generating the packages is done using the packaging tool '''makepack_dolibarr.pl'''. See next chapter for detailed operation done by this tool.

= The packaging of final releases =
When beta period end (no more serious bugs are reported and opened), the Dolibarr Yoda decide to start the freeze of final version. The name of the version is define to a value X.Y.Z.

Note: Only a Dolibarr Yoda can make this process.

* Firstly, final Unit Tests are run. If 1 test is wrong, process is stopped here and go back to beta phase.

Once all tests are ok, the following steps are done automatically using the packaging tool '''makepack_dolibarr.pl''' :

* The tool generate (or suggest the command to generate) the '''ChangeLog''' file. This file is commited with sources.
* The tool generates the file '''filelist-X.Y.Z.xml''' than contains the list of files of the version with a MD5 signature and value of version. This file is commited with sources.
* The tool add a '''Tag''' that is the name of version (so X.Y.Z) on all files of the official source repository. So starting from now, all files for the dedicated version are known and won't change anymore.
* The tool build all '''official distribution packages'''. Content of such packages match the content of the signature file since it is build during same process. The following packages are built:
** Package '''.zip''' (the main package)
** Package '''.tgz'''
** Autoinstaller Doliwamp '''.exe'''
** Autoinstaller for Debian/Ubuntu DoliDeb '''.deb'''
** Autoinstaller for Redhat, linuxmint, mandriva DoliRpm '''.rpm'''
* The tool upload the generated signature file '''filelist-X.Y.Z.xml''' on the official Dolibarr server. This file can be read by any installed application to check the integrity of the version (even one byte modified will change the signature).
* The tool upload the generated packaged into the '''official Dolibarr archive server''' to have them archived also in a binary form. This archives can be read from page https://www.dolibarr.org/files/stable/
* The tool upload the generated packaged into the '''mirror archive servers''' hosted at https://www.sourceforge.net. This is a mirror hosting, official references remain the Dolibarr archive area and are hosted by the Dolibarr team so at https://www.dolibarr.org/files/stable/.
* The release is also created on https://GitHub.com/Dolibarr/dolibarr
* Then people of the Dolibarr community send announcements on different channels (www.dolibarr.org, forums, social networks...).
* Starting from now, a new cycle can start. A new development period start from sources of the version.

Then a Dolibarr Yoda add 1 page (one page per version) onto the https://wiki.dolibarr.org to describe content of new version. This is the Release announcement. You can look at the page [[:Category:RoadMap]] for list of past announcements.

At any time, from the menu '''System Tools / About Dolibarr / Check integrity''', an admin user can check and validate integrity of its installed version compared to official reference. The tool calculate signature of each file and compare it with official signature. All removed and modified files are reported.

At any time, a developer can, from Github and using the '''Tag''' created at first step of release process, get all files of any stable version.