Phobos release cycle
Jonathan M Davis
newsgroup.d at jmdavisprog.com
Thu Oct 10 19:15:32 UTC 2019
On Thursday, October 10, 2019 6:47:06 AM MDT berni44 via Digitalmars-d
> As I started contributing I wonder about the release cycle of
> phobos. It looks like every two months, there is a new version.
> Is there any frozen state period or something I should know? Or
> can I just contribute and someone else takes care of me not
> adding bugs in the last seconds?!?
The current release cycle has a release approximately every month with it
alternating each month between a major and bug fix release. Prior to a major
release, master gets merged into stable, and the release is done from the
stable branch. Aside from when master is merged into stable prior to a major
release, the only things that get merged into stable are PRs for bug fixes,
and the month after a major release, a bug fix release is done with whatever
fixes have been merged into stable since the previous release.
Prior to a release, a beta is announced, and then at some point fairly soon
after that is the actual release. There really isn't any frozen period that
I'me aware of, though there may be more scrutiny towards what gets merged
into stable shortly before a release. Either way, there's definitely never a
freeze or the like for master.
Personally, I don't think that I've ever create any pull requests for
stable. I've generally just made all changes on master without worrying
about when the release is, though I think that at least some of the time, if
you make a bug fix PR against master, you might get asked to rebase it on
stable instead, since it's a bug fix. Either way, any changes that aren't
bug fixes would need to go to master.
- Jonathan M Davis
More information about the Digitalmars-d