Add CHANGELOG.md and version 0.9.0

- Add CHANGELOG.md following Keep a Changelog format
- Add DEVELOPMENT.md with project maintenance guidelines
- Update version to 0.9.0 in _version.py and pyproject.toml
- Add changelog link to README and docs navigation
- Add changelog maintenance guidelines to CONTRIBUTING.md

Author: minaskar

CHANGELOG.md

@@ -0,0 +1,49 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.9.0] - 2026-01-11
+
+### Added
+- Initial release of Tempest
+- Persistent Sampling (PS) algorithm implementation for accelerated Bayesian inference
+- Hierarchical Gaussian mixture clustering for multimodal distributions
+- MCMC proposal mechanisms with periodic and reflective boundary conditions
+- Multiprocessing and MPI parallelization support
+- Vectorized likelihood calculations for improved performance
+- State saving and loading functionality
+- Weighted posterior sample generation with trimming options
+- Bayesian model evidence (logZ) estimation with uncertainty
+- Multivariate Student's t-distribution fitting for heavy-tailed posteriors
+- Normalizing flow training for adaptive proposals
+- Dynamic ESS threshold adjustment
+- Effective and unique sample size metrics
+- Blobs support for storing additional likelihood data
+
+### Changed
+- Migrated from setup.py/setup.cfg to pyproject.toml for modern packaging
+- Removed torch from requirements (Python-only implementation)
+
+### Dependencies
+- numpy>=1.20.0
+- tqdm>=4.60.0
+- scipy>=1.4.0
+- dill>=0.3.8
+- multiprocess>=0.70.15
+
+### Platform
+- Python 3.8+
+
+### Testing
+- Unit tests for core functionality (1,251 lines of tests)
+- Integration tests for sampler features
+- Edge case and state management tests
+- CI/CD pipeline with Python 3.8-3.11 testing
+
+[Unreleased]: https://github.com/minaskar/tempest/compare/v0.9.0...HEAD
+[0.9.0]: https://github.com/minaskar/tempest/releases/tag/v0.9.0

CONTRIBUTING.md

@@ -11,9 +11,8 @@ responsive, I don't always get to every issue immediately.
 [Issues](https://github.com/minaskar/tempest/issues). If you're unable to find an
 open issue addressing the problem, [open a new
 one](https://github.com/minaskar/tempest/issues/new). Be sure to include a **title
-and clear description**, as much relevant information as possible, and the
-simplest possible **code sample** demonstrating the expected behavior that is
-not occurring.
+and clear description**, as much relevant information as possible, and the **simplest possible
+**code sample** demonstrating the expected behavior that is not occurring.
 
 ### Did you write a patch that fixes a bug?
 
@@ -24,10 +23,26 @@ if applicable.
 ### Do you intend to add a new feature or change an existing one?
 
 First, [open a new issue](https://github.com/minaskar/tempest/issues/new) and
-clearly describe your idea. We will then let you know if what you suggest 
+clearly describe your idea. We will then let you know if what you suggest
 aligns with the vision of Tempest. This way you might avoid doing unnecessary
 work and might even find some help from other people.
 
+### Updating the Changelog
+
+When contributing changes to Tempest, please update `CHANGELOG.md`:
+
+1. Add entries to the `[Unreleased]` section
+2. Use the appropriate category:
+   - `Added` for new features
+   - `Changed` for changes in existing functionality
+   - `Deprecated` for soon-to-be removed features
+   - `Removed` for now removed features
+   - `Fixed` for bug fixes
+   - `Security` for security vulnerability fixes
+3. Provide clear, user-friendly descriptions of changes
+
+The changelog follows the [Keep a Changelog](https://keepachangelog.com) format.
+
 Cheers,
 
 Minas

DEVELOPMENT.md

@@ -0,0 +1,139 @@
+# Development Guide
+
+This guide covers the development workflow and best practices for maintaining Tempest.
+
+## Changelog Maintenance
+
+The changelog follows the [Keep a Changelog](https://keepachangelog.com) format and documents all notable changes to the project.
+
+### When to Update
+
+Update `CHANGELOG.md` when:
+- Adding new features
+- Changing existing functionality
+- Fixing bugs
+- Deprecating or removing features
+- Addressing security vulnerabilities
+
+### Adding Entries
+
+1. Add entries to the `[Unreleased]` section at the top of `CHANGELOG.md`
+2. Use appropriate category:
+   - **Added**: New features
+   - **Changed**: Changes in existing functionality
+   - **Deprecated**: Soon-to-be removed features
+   - **Removed**: Now removed features
+   - **Fixed**: Bug fixes
+   - **Security**: Security vulnerability fixes
+
+3. Provide clear, user-friendly descriptions:
+   ```markdown
+   ### Added
+   - Support for custom proposal distributions
+   - New method for computing posterior summaries
+
+   ### Fixed
+   - Fixed memory leak in parallel MCMC sampling
+   - Corrected handling of NaN values in likelihood
+   ```
+
+### Release Process
+
+1. Update version in `tempest/_version.py`
+2. Move `[Unreleased]` entries to new version section:
+   ```markdown
+   ## [1.1.0] - 2026-01-15
+
+   ### Added
+   - (moved from Unreleased)
+   ```
+3. Add release date in ISO 8601 format (YYYY-MM-DD)
+4. Create git tag:
+   ```bash
+   git tag v1.1.0
+   git push origin v1.1.0
+   ```
+5. Push to main branch to trigger release workflow in `.github/workflows/release_to_pypi.yml`
+6. Create new `[Unreleased]` section for next version
+
+### Version Links
+
+After creating a release tag, update the version links at the bottom of `CHANGELOG.md`:
+```markdown
+[Unreleased]: https://github.com/minaskar/tempest/compare/v1.1.0...HEAD
+[1.1.0]: https://github.com/minaskar/tempest/releases/tag/v1.1.0
+[1.0.0]: https://github.com/minaskar/tempest/releases/tag/v1.0.0
+```
+
+## Testing
+
+### Running Tests
+
+```bash
+# Run all tests
+python -m unittest discover tests
+
+# Run specific test file
+python -m unittest tests.test_sampler
+
+# Run with pytest (if installed)
+pytest tests/
+```
+
+### Test Coverage
+
+Ensure new features include corresponding tests. Test files are in the `tests/` directory.
+
+## Code Style
+
+Tempest uses the following conventions:
+- Type hints where appropriate (Python 3.8+)
+- Docstrings following NumPy style
+- PEP 8 formatting
+
+## Dependencies
+
+Core dependencies are defined in:
+- `pyproject.toml` (project dependencies)
+- `requirements.txt` (simplified list)
+
+When adding new dependencies:
+1. Update both `pyproject.toml` and `requirements.txt`
+2. Consider impact on existing users
+3. Document in changelog
+
+## Documentation
+
+Documentation is built using MkDocs. To build locally:
+
+```bash
+# Install docs requirements
+pip install -r docs/requirements.txt
+
+# Serve docs
+mkdocs serve
+
+# Build docs
+mkdocs build
+```
+
+## Pull Requests
+
+When submitting a PR:
+1. Update CHANGELOG.md with relevant entries
+2. Add or update tests
+3. Ensure all tests pass
+4. Update documentation if needed
+5. Reference any related issues
+
+## Release Checklist
+
+Before creating a release:
+- [ ] Update version number in `tempest/_version.py`
+- [ ] Update CHANGELOG.md with all changes
+- [ ] Ensure all tests pass
+- [ ] Update documentation if needed
+- [ ] Tag release with `git tag v{version}`
+- [ ] Push tag to trigger PyPI release
+- [ ] Verify release on PyPI
+- [ ] Update GitHub Release notes (manual step)

README.md

@@ -19,7 +19,7 @@ in cosmology and astronomy, ``Tempest`` is user-friendly, flexible, and actively
 
 ## Documentation
 
-Read the docs at [tempest.readthedocs.io](https://tempest.readthedocs.io) for more information, examples and tutorials.
+Read the docs at [tempest.readthedocs.io](https://tempest.readthedocs.io) for more information, examples and tutorials. For a detailed list of changes, see the [CHANGELOG.md](https://github.com/minaskar/tempest/blob/main/CHANGELOG.md).
 
 ## Installation
 
@@ -42,7 +42,7 @@ python setup.py install
 For instance, if you wanted to draw samples from a 10-dimensional Rosenbrock distribution with a uniform prior, you would do something like:
 
 ```python
-import tempest as pc
+import tempest as tp
 import numpy as np
 
 n_dim = 10  # Number of dimensions
@@ -57,7 +57,7 @@ def log_likelihood(x):
             + (x[:,::2] - 1.0)**2.0, axis=1)
 
 # Create and run sampler
-sampler = pc.Sampler(
+sampler = tp.Sampler(
     prior_transform=prior_transform,
     log_likelihood=log_likelihood,
     n_dim=n_dim,

docs/index.md

@@ -39,7 +39,7 @@ Tempest is ideal for:
 Here's a simple example showing how to sample from a 10-dimensional Rosenbrock distribution:
 
 ```python
-import tempest as pc
+import tempest as tp
 import numpy as np
 from scipy.stats import uniform
 
@@ -55,7 +55,7 @@ def log_likelihood(x):
                    + (x[:, ::2] - 1.0)**2.0, axis=1)
 
 # Create the sampler
-sampler = pc.Sampler(
+sampler = tp.Sampler(
     prior_transform=prior_transform,
     log_likelihood=log_likelihood,
     n_dim=n_dim,
@@ -130,6 +130,14 @@ See the [Installation Guide](installation.md) for more details.
 
     [:octicons-arrow-right-24: Examples](examples/rosenbrock.md)
 
+-   :material-history:{ .lg .middle } **Changelog**
+
+    ---
+
+    Detailed history of changes for each version
+
+    [:octicons-arrow-right-24: Changelog](https://github.com/minaskar/tempest/blob/main/CHANGELOG.md)
+
 </div>
 
 ---

mkdocs.yml

@@ -105,3 +105,4 @@ nav:
     - Tools: api/tools.md
     - Clustering: api/cluster.md
   - Citation: citation.md
+  - Changelog: https://github.com/minaskar/tempest/blob/main/CHANGELOG.md

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "tempest"
-version = "1.0.0"
+version = "0.9.0"
 authors = [
     {name = "Minas Karamanis", email = "minaskar@gmail.com"},
 ]

tempest/_version.py

@@ -1 +1 @@
-version = "1.0.0"
+version = "0.9.0"