Skip to content

Commit d1b103b

Browse files
authored
update
1 parent 43a0f78 commit d1b103b

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/configuration/productive_usage.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -17,9 +17,9 @@ You can transport abap2UI5 to production just like any other ABAP development. T
1717
#### Stable Version
1818
The project will be continuously further developed. Therefore, there is no specific "stable" version. However, adjustments to the public APIs will be kept to a minimum to avoid frequent refactoring of apps. You can use the [releases](https://github.com/abap2ui5/abap2ui5/releases/) instead of pulling the main branch and update from time to time to reduce the effort needed for refactoring.
1919

20-
#### Renaming
21-
If you're starting new development but already have abap2UI5 apps running in production, and you're concerned about updating to the latest release, consider installing abap2UI5 multiple times in your system using the renaming feature. This way, you can safely continue development without affecting your existing apps in production.
22-
2320
#### Transport
2421
Install the project using abapGit into your development system. Then, use the normal transport process for deployment to production:
2522
![alt text](image-3.png){ width=80% }
23+
24+
#### Renaming
25+
If you're starting new development but already have abap2UI5 apps running in production, and you're concerned about updating to the latest release, consider installing abap2UI5 multiple times in your system using the renaming feature. This way, you can safely continue development without affecting your existing apps in production.

0 commit comments

Comments
 (0)