[
https://issues.apache.org/jira/browse/UNOMI-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Sinovassin-Naïk updated UNOMI-829:
-------------------------------------------
Description:
The goal of this ticket is to update many libraries as possible in the unomi
codebase.
Begin with libraries that are expected to be simple to upgrade, do not try
updating complex libraries in the context of this ticket.
Upgrade strategy:
* Look at library usage, see if it can be easily removed.
* If not, update the library and trigger a build.
* If the build fails, estimate effort to fix, if fix seems easy, timebox it to
30mn MAX.
* If update is not easy, detail (briefly) why in this ticket and move on to
the next library.
Versioning strategy:
* Try updating to the last released version of the library (except if tagged
beta or alpha).
* If too many breaking changes, if a maintenance branch exists for that
library on the same major digit that the version used in unomi, and if this
version is still maintained (updated less than 2 years ago), update to the
latest released in this maintenance branch and create a ticket to update the
library to the latest released version.
* If not possible, detail briefly why in this ticket and create a ticket to
update or replace the library.
was:
The goal of this ticket is to update as many libraries as possible in the unomi
codebase.
Begin with libraries that are expected to be simple to upgrade, do not try
updating complex libraries in the context of this ticket.
Upgrade strategy:
* Look at library usage, see if it can be easily removed.
* If not, update the library and trigger a build.
* If the build fails, estimate effort to fix, if fix seems easy, timebox it to
30mn MAX.
* If update is not easy, detail (briefly) why in this ticket and move on to
the next library.
Versioning strategy:
* Try updating to the last released version of the library (except if tagged
beta or alpha).
* If too many breaking changes, if a maintenance branch exists for that
library on the same major digit that the version used in unomi, and if this
version is still maintained (updated less than 2 years ago), update to the
latest released in this maintenance branch and create a ticket to update the
library to the latest released version.
* If not possible, detail briefly why in this ticket and create a ticket to
update or replace the library.
> Upgrade the dependencies version
> --------------------------------
>
> Key: UNOMI-829
> URL: https://issues.apache.org/jira/browse/UNOMI-829
> Project: Apache Unomi
> Issue Type: Task
> Components: unomi(-core)
> Reporter: Jonathan Sinovassin-Naïk
> Assignee: Jonathan Sinovassin-Naïk
> Priority: Major
>
> The goal of this ticket is to update many libraries as possible in the unomi
> codebase.
> Begin with libraries that are expected to be simple to upgrade, do not try
> updating complex libraries in the context of this ticket.
> Upgrade strategy:
> * Look at library usage, see if it can be easily removed.
> * If not, update the library and trigger a build.
> * If the build fails, estimate effort to fix, if fix seems easy, timebox it
> to 30mn MAX.
> * If update is not easy, detail (briefly) why in this ticket and move on to
> the next library.
> Versioning strategy:
> * Try updating to the last released version of the library (except if tagged
> beta or alpha).
> * If too many breaking changes, if a maintenance branch exists for that
> library on the same major digit that the version used in unomi, and if this
> version is still maintained (updated less than 2 years ago), update to the
> latest released in this maintenance branch and create a ticket to update the
> library to the latest released version.
> * If not possible, detail briefly why in this ticket and create a ticket to
> update or replace the library.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
