facebook/TestSlide

Automate release process

Open

#1 opened on Oct 3, 2018

View on GitHubContributor guide
 (1 comment) (0 reactions) (1 assignee)Python (58 forks)auto 404
Buildenhancementhelp wanted

Repository metrics

Stars
 (147 stars)
PR merge metrics
 (PR metrics pending)

Description

This is mostly manual as described at RELEASE.md. We need to:

  • Using semantic versioning, be able to do major, minor and patch releases, calculating the new version based on the previous.
  • Unify version at setup.py and docs/conf.py.
  • Ensure Travis CI build is OK for new release.
  • Ensure readthedocs.org build is OK for each release.

Contributor guide

Research direction
Investigate the existing RELEASE.md to understand the manual steps, then implement an automated script that uses semantic versioning to determine the new version, updates setup.py and docs/conf.py, and triggers CI builds on Travis CI and readthedocs. Consider using tools like bumpversion or a custom script.
Tech stack
python
Domain
devops
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50