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

Verification of what happens when trying to upgrade from a erroneous version #54

Open
jthambly opened this issue Mar 2, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@jthambly
Copy link
Owner

jthambly commented Mar 2, 2021

With the following versions, we cannot generate the source to determine which files should be removed.

1.10.0.Final
1.11.0.Final
1.11.1.Final

Although we might not be able to use the above versions for testing, automated testing should also test for instances where it needs to proceed with the backup method of updating project files.

This will not be done as apart of the GitHub Action work, instead it will be associated with issue #13

@jthambly jthambly added the enhancement New feature or request label Mar 2, 2021
@jthambly jthambly self-assigned this Mar 2, 2021
@jthambly jthambly added this to the Filesystem clean up milestone Mar 3, 2021
@jthambly
Copy link
Owner Author

jthambly commented Mar 7, 2021

For this to be achieved we will need a way to verify the filesystem post update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant