[dmd-internals] 1st Biweekly Sprint Planning

[Martin Nowak via dmd-internals]

On 07/10/2015 03:57 PM, Andrei Alexandrescu wrote:
> So whenever we start a new release, we branch master into stable. Why,
> then, is it unadvisable to just continue business as usual in master?
> Sorry for the silly question, just learning the ropes. -- Andrei

It's not unadvisable, except for competing with dev resources.
The problem I was talking about is the buisness as usual part.

Right now features often land as multiple PRs against master, or some
feature gets merged under the condition of a follow-up PR.
Sometimes those PRs spread over more than the 2 month release period.

We then end up with lots of incomplete features when merging master into
stable. It's not feasible for me or anyone to track every development
activity.

The cleanest solution would be to complete features in a branch to a
releasable state and only then merge them, i.e. stop developing on master.

On reason for splitting up features into multiple PRs is to make them
easier to review. This could be done by breaking down stories/features
into smaller parts, and doing a review on the feature branch when a
milestone has been completed.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.puremagic.com/pipermail/dmd-internals/attachments/20150710/fad1748e/attachment.sig>