Update definition of done

work/definition-of-done.md

@@ -1,6 +1,7 @@
 # Definition of Done
 
-This document outlines the specific criteria that must be met for a new releasable increment of our application to be considered complete. It serves as a checklist for developers and AI agents to ensure quality and consistency in our releases.
+This document outlines the specific criteria that must be met for a new increment of our application to be considered releasable.
+It serves as a checklist for developers and AI agents to ensure quality and consistency in our releases.
 
 ## Code Quality and Testing
 
@@ -10,47 +11,36 @@ This document outlines the specific criteria that must be met for a new releasab
   - Running pre-commit hooks
   - Running non-integration tests with `pytest`
 - [ ] All new functionality has corresponding unit tests in the `tests/` directory
-- [ ] No `TODO` comments remain in the code related to the current work
 - [ ] GitHub Actions CI workflow passes on the main branch
 
 ## Documentation
 
-- [ ] Docstrings are added/updated for all new/modified functions, classes, and modules
 - [ ] README.md is updated with any new features, dependencies, or usage instructions
 - [ ] Any new environment variables are added to both `.env.example` and `mongo/.env.default`
-- [ ] `docs/software_architecture.md` is updated if there are architectural changes
+- [ ] `docs/software_architecture.md` is up-to-date with the current architecture and design forces.
 
 ## Functionality
 
 - [ ] All new CLI commands are implemented in `src/floridayvine/commands/` and properly integrated in `src/floridayvine/__main__.py`
-- [ ] New database operations are added to `src/floridayvine/persistence.py` and tested
-- [ ] MinIO operations in `src/floridayvine/minio.py` are updated and tested if affected
-- [ ] Floriday-related functionality in `src/floridayvine/floriday/` is updated and tested if affected
 
 ## Performance and Security
 
 - [ ] No sensitive information (API keys, passwords) is hardcoded or logged
 - [ ] All database queries are optimized and indexed appropriately
-- [ ] Large data operations use appropriate batching or streaming techniques
 - [ ] Environment variables are used for all configuration options
 
 ## DevOps and Deployment
 
 - [ ] `Dockerfile` and `docker-compose.yml` are updated if there are new dependencies or services
 - [ ] `requirements-dev.txt` is updated with any new development dependencies
-- [ ] Version number in `src/floridayvine/commands/version.py` is incremented appropriately
-- [ ] `floridayvine-crontab` is updated if there are changes to scheduled tasks
+- [ ] Version number is incremented appropriately
 - [ ] Configuration files (.flake8, .pre-commit-config.yaml, .vscode/settings.json) are up-to-date and committed to the repository
 
 ## Cross-compatibility
 
 - [ ] Application runs successfully on both development and production environments
 - [ ] Any new dependencies are added to `pyproject.toml` and are compatible with both Linux and macOS
 
-## User Acceptance
-
-- [ ] New features or changes have been demonstrated and approved by the product owner
-
 ## Release and Deployment
 
 - [ ] Code and documentation are pushed to the central code repository
@@ -61,7 +51,6 @@ This document outlines the specific criteria that must be met for a new releasab
 ## Final Checks
 
 - [ ] GitHub Actions CI workflow passes on the main branch, running all quality checks
-- [ ] `scripts/verify_credentials.sh` runs successfully with the updated code
 - [ ] Application can be built and run using `docker-compose up` without errors
 
 ## Undone for now
@@ -71,5 +60,9 @@ The following items are considered important for future releases but are not cur
 - [ ] Implement test coverage measurement and maintain or improve coverage (verify with coverage tool)
 - [ ] Create a script to automatically check if all environment variables in `.env.example` and `mongo/.env.default` are up to date
 - [ ] Implement a zipped version of the code for download as part of the release process
+- [ ] Test the application in both development and production environments.
+- [ ] Cross platform compatibility
+  - [ ] Linux
+  - [ ] Mac OSX
 
 This Definition of Done should be reviewed and updated periodically to reflect the evolving needs of the project. Items from the "Undone for now" section should be considered for inclusion in the main DoD as they become implemented and integrated into our development process.