Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

method to check if projet is compatible with target version #4078

Closed
wants to merge 2 commits into from

Conversation

nworr
Copy link
Contributor

@nworr nworr commented Jan 19, 2024

Projet written for a version N are supported until N+2 version

the method can be usefull for testing projets before upgrade

Funded by 3liz

@github-actions github-actions bot added this to the 3.8.0 milestone Jan 19, 2024
@nworr nworr requested review from Gustry and rldhont January 19, 2024 10:13
@nworr nworr added backport master If the PR was against a release branch backport release_3_7 and removed backport master If the PR was against a release branch labels Jan 19, 2024
Copy link
Member

@Gustry Gustry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I totally understand the PR, it works these days because we have followed this rule until now.

With one release per year, this was giving 2 years of time for a "sleeping project" to be displayed.

  • 3.4 : 2020
  • 3.5 : 2021
  • 3.6 : 2022
  • 3.7 : 2023

The variable lizmapWebClientTargetVersion in the conf file was somehow edited at the time of the release of X.Y.0 more or less to let the user enough time with these projects and the variable lizmapWebClientTargetVersion could be adjusted accordingly.

With the planned new release schedule with 2 releases per year, this is considerably reducing the timeframe (see internal issues/232#note_67164). Increasing the release schedule.

With this PR, it will be now hardcoded N+2. If we still go this way, I would rephrase the maybe as well in the conf file. Or I would even remove the configuration file and the function getLizmapWebClientTargetVersion because this would be only using the current LWC version +2 or -2 (depending of the context)

@@ -2313,6 +2313,19 @@ public function needsUpdateWarning()
return false;
}

/**
* test if provided version (int format 30520).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess this docstring needs to be rephrased ?

*/
public function isCompatibleWithVersion(int $targetVersion): bool
{
// the projet version written for N are supported until N+2
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
// the projet version written for N are supported until N+2
// the project version written for version N are supported until version N+2

@nworr nworr marked this pull request as draft January 19, 2024 14:38
Gustry added a commit that referenced this pull request Jan 22, 2024
The minimum version allowed is determined when we are ready to release the X.Y.0 version, according to the timeframe, to let enough time for users to upgrade their project, see discussion PR #4078
@nworr nworr closed this Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants