docs: Update RELEASE_MEMO with current process

- Add branch structure section (master for 2.1, maint/2.0 for maintenance)
- Add documentation release process section
- Update conda-forge section with dependency notes
- Remove @drewyangdev and @guzman-raphael from maintainers
- Add links to datajoint-docs and docs.datajoint.com

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: dimitri-yatsenko

RELEASE_MEMO.md

@@ -1,5 +1,19 @@
 # DataJoint Release Memo
 
+## Branch Structure
+
+| Branch | Purpose | Version |
+|--------|---------|---------|
+| `master` | Main development | 2.1.x |
+| `maint/2.0` | Maintenance releases | 2.0.x |
+
+For 2.0.x bugfixes:
+1. Commit to `maint/2.0`
+2. Tag and release as v2.0.x
+3. Cherry-pick to master if applicable
+
+---
+
 ## Writing Release Notes
 
 Good release notes help users understand what changed and whether they need to take action.
@@ -37,7 +51,7 @@ Organize changes into these categories (in order):
 - Fixed incorrect NULL handling in aggregations (#234)
 
 ### Full Changelog
-https://github.com/datajoint/datajoint-python/compare/v0.14.3...v2.0.0
+https://github.com/datajoint/datajoint-python/compare/v2.0.0...v2.1.0
 ```
 
 ### Guidelines
@@ -67,21 +81,23 @@ Ensure PRs have appropriate labels before merging.
 
 ### Steps
 
-1. **Run "Manual Draft Release" workflow** on GitHub Actions
-2. **Edit the draft release**:
-   - Change release name to `Release 2.0.0`
-   - Change tag to `v2.0.0`
-3. **Publish the release**
-4. Automation will:
-   - Update `version.py` to `2.0.0`
+1. **Add labels to merged PRs** for release-drafter categorization
+2. **Run "Manual Draft Release" workflow** on GitHub Actions
+3. **Edit the draft release**:
+   - Set release name to `Release X.Y.Z`
+   - Set tag to `vX.Y.Z`
+   - Review and edit release notes
+4. **Publish the release**
+5. Automation will:
+   - Update `version.py` to `X.Y.Z`
    - Build and publish to PyPI
    - Create PR to merge version update back to master
 
 ### Version Note
 
-The release drafter computes version from the previous tag (`v0.14.6`), so it would generate `0.14.7` or `0.15.0`. You must **manually edit** the release name to include `2.0.0`.
+The release drafter computes version from the previous tag. You may need to **manually edit** the release name for major version changes.
 
-The regex on line 42 of `post_draft_release_published.yaml` extracts version from the release name:
+The regex in `post_draft_release_published.yaml` extracts version from the release name:
 ```bash
 VERSION=$(echo "${{ github.event.release.name }}" | grep -oP '\d+\.\d+\.\d+')
 ```
@@ -99,7 +115,7 @@ Conda-forge has **automated bots** that detect new PyPI releases and create PRs
 1. **You publish to PyPI** (via the GitHub release workflow)
 2. **regro-cf-autotick-bot** detects the new version within ~24 hours
 3. **Bot creates a PR** to the feedstock with updated version and hash
-4. **Maintainers review and merge** (you're listed as a maintainer)
+4. **Maintainers review and merge**
 5. **Package builds automatically** for all platforms
 
 ### Manual Update (if bot doesn't trigger)
@@ -110,7 +126,7 @@ If the bot doesn't create a PR, manually update the feedstock:
 
 2. **Edit `recipe/meta.yaml`**:
    ```yaml
-   {% set version = "2.0.0" %}
+   {% set version = "2.1.0" %}
 
    package:
      name: datajoint
@@ -126,55 +142,86 @@ If the bot doesn't create a PR, manually update the feedstock:
 
 3. **Get the SHA256 hash**:
    ```bash
-   curl -sL https://pypi.org/pypi/datajoint/2.0.0/json | jq -r '.urls[] | select(.packagetype=="sdist") | .digests.sha256'
+   curl -sL https://pypi.org/pypi/datajoint/2.1.0/json | jq -r '.urls[] | select(.packagetype=="sdist") | .digests.sha256'
    ```
 
-4. **Update license** (important for 2.0!):
+4. **Check dependencies** match `pyproject.toml`:
    ```yaml
-   about:
-     license: Apache-2.0  # Changed from LGPL-2.1-only
-     license_file: LICENSE
+   requirements:
+     host:
+       - python {{ python_min }}
+       - pip
+       - setuptools >=62.0
+     run:
+       - python >={{ python_min }}
+       - numpy
+       - pandas
+       - pymysql >=1.0
+       - minio
+       - packaging
+       # ... etc
    ```
 
 5. **Submit PR** to the feedstock
 
-### Action Items for 2.0 Release
+### Verification
 
-1. **First**: Publish to PyPI via GitHub release (name it "Release 2.0.0")
-2. **Wait**: ~24 hours for conda-forge bot to detect
-3. **Check**: [datajoint-feedstock PRs](https://github.com/conda-forge/datajoint-feedstock/pulls) for auto-PR
-4. **Review**: Ensure license changed from LGPL to Apache-2.0
-5. **Merge**: As maintainer, approve and merge the PR
+After release:
+```bash
+conda search datajoint -c conda-forge
+```
 
-### Timeline
+---
 
-| Step | When |
-|------|------|
-| PyPI release | Day 0 |
-| Bot detects & creates PR | Day 0-1 |
-| Review & merge PR | Day 1-2 |
-| Conda-forge package available | Day 1-2 |
+## Documentation Release Process
 
-### Verification
+Documentation is hosted at [docs.datajoint.com](https://docs.datajoint.com) and built from [datajoint-docs](https://github.com/datajoint/datajoint-docs).
 
-After release:
+### How Documentation Builds Work
+
+The documentation build:
+1. Checks out `datajoint-python` from the `master` branch
+2. Uses mkdocstrings to generate API docs from source docstrings
+3. Builds static site with MkDocs
+4. Deploys to `gh-pages` branch
+
+### Triggering a Documentation Build
+
+Documentation rebuilds automatically when:
+- Changes are pushed to `datajoint-docs` main branch
+
+To manually trigger a rebuild (e.g., after updating docstrings in datajoint-python):
 ```bash
-conda search datajoint -c conda-forge
-# Should show 2.0.0
+gh workflow run development.yml --repo datajoint/datajoint-docs
 ```
 
+Or use the "Run workflow" button in GitHub Actions.
+
+### Updating Documentation
+
+1. **For docstring changes**: Update docstrings in `datajoint-python`, then trigger a docs rebuild
+2. **For content changes**: Edit files in `datajoint-docs/src/`, push to main
+3. **Docstring style**: Use NumPy-style docstrings (see CONTRIBUTING.md)
+
+### Verification
+
+After build completes:
+- Check [docs.datajoint.com](https://docs.datajoint.com)
+- Verify API reference pages show updated content
+
 ---
 
 ## Maintainers
 
 - @datajointbot
 - @dimitri-yatsenko
-- @drewyangdev
-- @guzman-raphael
 - @ttngu207
 
 ## Links
 
+- [datajoint-python on GitHub](https://github.com/datajoint/datajoint-python)
+- [datajoint-docs on GitHub](https://github.com/datajoint/datajoint-docs)
 - [datajoint-feedstock on GitHub](https://github.com/conda-forge/datajoint-feedstock)
 - [datajoint on Anaconda.org](https://anaconda.org/conda-forge/datajoint)
 - [datajoint on PyPI](https://pypi.org/project/datajoint/)
+- [docs.datajoint.com](https://docs.datajoint.com)