8
.. i18n: Explanation of the Versions
9
.. i18n: +++++++++++++++++++++++++++
11
Explanation of the Versions
12
+++++++++++++++++++++++++++
14
.. i18n: The development of OpenERP follows two distinct branches:
16
The development of OpenERP follows two distinct branches:
18
.. i18n: * Stable: a new version is published every year. This version is intended to
19
.. i18n: be put in production, only bugfixes are applied in this version.
20
.. i18n: * Development (sometimes called the trunk): It will contain all the latest
21
.. i18n: functionalities and modules. It is intended for testing purpose only, until
22
.. i18n: it is stabilized as the next stable version.
24
* Stable: a new version is published every year. This version is intended to
25
be put in production, only bugfixes are applied in this version.
26
* Development (sometimes called the trunk): It will contain all the latest
27
functionalities and modules. It is intended for testing purpose only, until
28
it is stabilized as the next stable version.
42
.. i18n: A new stable version is published every year. Example:
44
A new stable version is published every year. Example:
46
.. i18n: * May: Community Meeting
48
.. i18n: - Define missing and urgent bugfixes and features
49
.. i18n: - Tiny and Partners Choose modules from contrib and extra addons that will integrate official addons
50
.. i18n: - Define precise timeline and tasks assignation
51
.. i18n: * July: Branch the trunk to the new stable version
53
.. i18n: - You can not add new features in the futur stable
54
.. i18n: - Only bugfixes are accepted in this new branch
55
.. i18n: * August: Publish first releases candidates
56
.. i18n: * September: Publish the new stable version
58
* May: Community Meeting
60
- Define missing and urgent bugfixes and features
61
- Tiny and Partners Choose modules from contrib and extra addons that will integrate official addons
62
- Define precise timeline and tasks assignation
63
* July: Branch the trunk to the new stable version
65
- You can not add new features in the futur stable
66
- Only bugfixes are accepted in this new branch
67
* August: Publish first releases candidates
68
* September: Publish the new stable version
76
.. i18n: Community Meeting
77
.. i18n: """""""""""""""""
82
.. i18n: Participants: Everybody
84
Participants: Everybody
90
.. i18n: * Define exact release timeline
91
.. i18n: * Define required tasks for new version
92
.. i18n: * Select official addons
94
* Define exact release timeline
95
* Define required tasks for new version
96
* Select official addons
98
.. i18n: Branching to new stable
99
.. i18n: """""""""""""""""""""""
101
Branching to new stable
102
"""""""""""""""""""""""
108
.. i18n: * After branching, no new features accepted
109
.. i18n: * Bugfix period
111
* After branching, no new features accepted
114
.. i18n: Release Candidates
115
.. i18n: """"""""""""""""""
124
.. i18n: * Publish a version to be tested by the community
125
.. i18n: * Different release candidates, every 2 weeks
127
* Publish a version to be tested by the community
128
* Different release candidates, every 2 weeks
130
.. i18n: Stable Version
131
.. i18n: """"""""""""""
140
.. i18n: * Publish when everything is perfect
142
* Publish when everything is perfect
144
.. i18n: Creating Screen cast for OpenERP
145
.. i18n: """"""""""""""""""""""""""""""""""
146
.. i18n: Point to be noted to start with Screen cast for OpenERP.
148
Creating Screen cast for OpenERP
149
""""""""""""""""""""""""""""""""""
150
Point to be noted to start with Screen cast for OpenERP.
152
.. i18n: * Make demo in eTiny *Webclient*.(Its not compulsory)
154
.. i18n: * We have a specific software to create screen cast. The name is "Screen Flash". It works in windows.
155
.. i18n: You can purchas license copy of Screen Flash. So, do not use with fake / crack ID.
157
.. i18n: * For linux, one can use "gtk-Record-my-desktop", but preferable is to use "Screen Flash" on windows to get good result.
159
.. i18n: * The resolution of your screen at the time of recording should be 800 X 600 for screen cast.
161
.. i18n: * The speed of recording (cursor / pointer) should be very slow (wait for 1-2 second between to clicks), as you are experts so you know the process, but we are preparing these screen cast for the people, who are not used to with OpenERP. The purpose of screen cast is to make them understand and can learn the process by themselves.
163
.. i18n: * At the time of typing, be careful for not committing any mistake, avoid erase and retype.
165
.. i18n: * Close all your other program / application / software running before you start processing for screen cast.
167
.. i18n: * For windows, screen flash software, kindly configure your short cut for better clarity.
169
.. i18n: * Auto hide your task bar before starting screen flash on windows/ gtk-Record-my-desktop on linux.
171
.. i18n: * Always maximize your window at the time of screen cast, so it can capture all the visible portion with perfection and to avoid other part of unused screen object.
173
.. i18n: * First list out all steps to show, and remember all steps. At the time of recording you must be clear that what will be the next step to show. so you do not hesitate in between choosing inappropriate steps.
175
.. i18n: * If required, kindly prepare demo data that you want to show for better understanding of users, and also it will not take too much time to type it during recording.
177
.. i18n: * For required and useful fields highlight the tool-tip and stay for sometimes (At least once we can read it slowly) so the other people can read it and know the exact use of that field.
179
.. i18n: * One can edit screen cast, if prepared in Screen Flash software on windows. But its better to avoid it by making it proper from the start.
181
* Make demo in eTiny *Webclient*.(Its not compulsory)
183
* We have a specific software to create screen cast. The name is "Screen Flash". It works in windows.
184
You can purchas license copy of Screen Flash. So, do not use with fake / crack ID.
186
* For linux, one can use "gtk-Record-my-desktop", but preferable is to use "Screen Flash" on windows to get good result.
188
* The resolution of your screen at the time of recording should be 800 X 600 for screen cast.
190
* The speed of recording (cursor / pointer) should be very slow (wait for 1-2 second between to clicks), as you are experts so you know the process, but we are preparing these screen cast for the people, who are not used to with OpenERP. The purpose of screen cast is to make them understand and can learn the process by themselves.
192
* At the time of typing, be careful for not committing any mistake, avoid erase and retype.
194
* Close all your other program / application / software running before you start processing for screen cast.
196
* For windows, screen flash software, kindly configure your short cut for better clarity.
198
* Auto hide your task bar before starting screen flash on windows/ gtk-Record-my-desktop on linux.
200
* Always maximize your window at the time of screen cast, so it can capture all the visible portion with perfection and to avoid other part of unused screen object.
202
* First list out all steps to show, and remember all steps. At the time of recording you must be clear that what will be the next step to show. so you do not hesitate in between choosing inappropriate steps.
204
* If required, kindly prepare demo data that you want to show for better understanding of users, and also it will not take too much time to type it during recording.
206
* For required and useful fields highlight the tool-tip and stay for sometimes (At least once we can read it slowly) so the other people can read it and know the exact use of that field.
208
* One can edit screen cast, if prepared in Screen Flash software on windows. But its better to avoid it by making it proper from the start.