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?!?

On Thursday, 10 October 2019 at 12:47:06 UTC, berni44 wrote:
> 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?!?

There is a beta version before "actual" release, so that is the "frozen" period. And even after that the "point releases" fix more serious bugs so they do not have to wait for the next major release.

On Thursday, 10 October 2019 at 12:47:06 UTC, berni44 wrote:
> Is there any frozen state period or something I should know?

The release cycle is 2 months now; usually, Martin Nowak merges master into stable shortly before the first beta, and that's then the branch for the upcoming release (incl. betas, release candidates, point releases). All development in master is postponed to the next release, until master is merged into stable again (and of course all fixes in stable into master).

On Thursday, October 10, 2019 6:47:06 AM MDT berni44 via Digitalmars-d wrote:
> 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

On Thursday, 10 October 2019 at 12:47:06 UTC, berni44 wrote:
> 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?!?

https://dlang.org/changelog/release-schedule.html

tl;dr: target master for features or potential breakage, stable for safe bug fixes.

On Thursday, 10 October 2019 at 19:15:32 UTC, Jonathan M Davis wrote:
> The current release cycle has a release approximately every month with it alternating each month between a major and bug fix release. [...]

OK, thanks to all of you. I think I got it now. :-)

On Thursday, 10 October 2019 at 19:54:22 UTC, Seb wrote:
> tl;dr: target master for features or potential breakage, stable

I though stable was only meant for fixes of regressions:
"Regressions go to stable, and everything else to master"
https://github.com/dlang/dmd/blob/master/CONTRIBUTING.md

Your statement seems more in line with what actually happens in practice though.

On Thursday, 10 October 2019 at 20:33:05 UTC, Dennis wrote:
> On Thursday, 10 October 2019 at 19:54:22 UTC, Seb wrote:
>> tl;dr: target master for features or potential breakage, stable
>
> I though stable was only meant for fixes of regressions:
> "Regressions go to stable, and everything else to master"
> https://github.com/dlang/dmd/blob/master/CONTRIBUTING.md
>
> Your statement seems more in line with what actually happens in practice though.

Yep, the full article:

https://wiki.dlang.org/DIP75#Branching_strategy