Lines Matching +full:release +full:-

1 # Release Process for Delete Page Guard Plugin
3 This document describes the complete release process for the Delete Page Guard DokuWiki plugin, inc…
7 The plugin uses a professional release workflow with:
9 - Centralized version management
10 - Automated testing and validation
11 - Distribution packaging
12 - Git integration
13 - Semantic versioning
17 Before starting a release, ensure you have:
19 - PHP 7.4+ installed
20 - Git repository properly configured
21 - All changes committed and pushed
22 - Tests passing
24 ## Release Workflow
26 ### 1. Prepare for Release
28 First, ensure the codebase is ready for release:
54 - **Patch version** (x.y.Z): Bug fixes, security patches, minor improvements
55 - **Minor version** (x.Y.z): New features, backward-compatible changes
56 - **Major version** (X.y.z): Breaking changes, major refactoring
61 make version VERSION=1.0.1 # Bug fix release
62 make version VERSION=1.1.0 # Feature release
63 make version VERSION=2.0.0 # Major release with breaking changes
66 **Note:** The current version is 1.0.0, which represents the initial stable release.
70 - Update `version.php` with new version and current date
71 - Update `plugin.info.txt` with version information
72 - Validate the new version format
73 - Show what files were modified
77 After version update, manually update release documentation:
81 Create or update `CHANGELOG.md` with release notes:
86 ## [x.y.z] - YYYY-MM-DD
90 - New features
94 - Modified functionality
98 - Bug fixes
102 - Security improvements
109 - Current feature list
110 - Updated installation instructions
111 - Correct version references
113 ### 4. Complete Release Workflow
115 Use the automated release workflow:
118 # Complete release preparation
119 make release VERSION=x.y.z
139 git add -A
141 # Commit the release
142 git commit -m "Release version x.y.z"
144 # Tag the release
151 git push origin main --tags
164 - Run tests and syntax checks
165 - Create a clean distribution directory in `dist/deletepageguard-x.y.z/`
166 - Include only necessary files for DokuWiki installation
167 - Provide installation instructions
171 - `action.php` - Core plugin functionality
172 - `admin.php` - Administrative interface
173 - `plugin.info.txt` - Plugin metadata
174 - `LICENSE.md` - GPL v2 license
175 - `conf/` - Configuration files
176 - `lang/` - Language files
184 ls -la dist/deletepageguard-x.y.z/
202 ### Release Commands
207 make release VERSION=x.y.z # Complete release workflow
226 'date' => 'YYYY-MM-DD',
236 The `build/update-version.php` script automatically:
238 - Updates version across all relevant files
239 - Sets current date
240 - Validates semantic version format
241 - Reports all changes made
249 - Test cases covering all functionality
250 - Pattern validation and matching
251 - Security features and edge cases
252 - Cross-platform compatibility
253 - No DokuWiki installation required for testing
257 Each release is validated through:
259 - PHP syntax checking
260 - Comprehensive test suite execution
261 - Pattern validation testing
262 - Security vulnerability checks
270 - Core plugin files (`action.php`, `admin.php`)
271 - Configuration files (`conf/`)
272 - Language files (`lang/`)
273 - Documentation (`LICENSE.md`)
274 - Plugin metadata (`plugin.info.txt`)
310 php -r "var_dump(include 'version.php');"
327 1. **Always test before release**: Run `make test` and `make check`
334 ## Release Checklist
336 - [ ] All tests pass (`make test`)
337 - [ ] Syntax check clean (`make check`)
338 - [ ] Version updated (`make version VERSION=x.y.z`)
339 - [ ] CHANGELOG.md updated with release notes
340 - [ ] README.md reviewed and current
341 - [ ] Changes committed and pushed
342 - [ ] Release tagged (`git tag vx.y.z`)
343 - [ ] Distribution package created (`make dist`)
344 - [ ] Distribution verified and tested
345 - [ ] Release pushed with tags (`git push origin main --tags`)
349 For questions about the release process:
351 - Review this documentation
352 - Check Makefile help (`make help`)
353 - Examine test output for issues
354 - Refer to git history for previous releases