You're awesome! We're giving you commit bits.

[ezyang]

Hello @thumphries, @sjakobi, @accraze, @headprogrammingczar, @randen, @aisamanra, @kolmodin, @mightybyte, @gbaz, @garetxe, @komadori, @mgsloan, @lukexi, @mpkh, @pra85, @tvestelind, @corngood, @gelisam,

You're receiving this message because you recently contributed to Cabal. We value your contribution to Cabal, and so in the style of The Pull Request Hack, we are giving you commit bits. There are a few common sense rules about pushing to master (e.g., https://github.com/haskell/cabal#conventions — especially, keep the CI green and PR big changes before pushing), but mostly, be bold!

This is a new experiment for all of us and if there are things that are confusing and unclear please ask, we will try to clarify as much as possible.

P.S. If you know anyone I missed, please let me know.

[23Skidoo]

Also added @Blaisorblade since he's the one who originally proposed this idea and has contributed some patches in the past.

[kolmodin]

Wohoo! First of all, thanks! :)

This also gives access to edit in the issue tracker. I've missed this in the past when I've seen {mis,un}labeled issues. Great!

So you do most development against master but bigger features in feature branches?
New releases are always made from master?

[23Skidoo]

@kolmodin

So you do most development against master but bigger features in feature branches?

Basically yes, big features are expected to go through code review before merging.

New releases are always made from master?

From release branches. For example, all 1.24 releases are made from the 1.24 branch.

[kolmodin]

From release branches. For example, all 1.24 releases are made from the 1.24 branch.

Ah, ok. And the release manager is responsible for merging fixes and updates from master to the release branch for minor releases?

[ezyang]

Yeah, at the moment only the release manager is supposed to touch the stable branches. But if that is not working for people we can reconsider.

FWIW, I know some people work on big features by running feature branches but my personal style is maintaining patchsets which I continually rebase on HEAD, the idea being that self-contained patches are easier to CR. I'm not sure we should enforce this on everyone though.

[phadej]

CR?

Sent from my iPhone

On 20 Jul 2016, at 19:56, Edward Z. Yang notifications@github.com wrote:

Yeah, at the moment only the release manager is supposed to touch the stable branches. But if that is not working for people we can reconsider.

FWIW, I know some people work on big features by running feature branches but my personal style is maintaining patchsets which I continually rebase on HEAD, the idea being that self-contained patches are easier to CR. I'm not sure we should enforce this on everyone though.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[ezyang]

Code review!

[ezyang]

@acfoltzer added!

[gelisam]

Wow, this is a very active project! My inbox is already overflowing with
GitHub notifications from the project, mostly about features I've never
heard of. I guess I'll keep lurking until I get a better idea of what's
going on, or until I see a bug go by which I think I'd be able to fix.

Thanks for adding me!

On Jul 21, 2016 12:38 AM, "Edward Z. Yang" notifications@github.com wrote:

@acfoltzer https://github.com/acfoltzer added!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#3567 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAC_aCE0f7-9ZsqGFiy2w-njTYb-P-dJks5qXvexgaJpZM4JOGld
.

[ezyang]

@gelisam Sorry about the spam! If you (or anyone else) don't want to get notifications for ALL tickets, I think the "unwatch" button should work. But also feel free to lurk / ask questions!

[23Skidoo]

Also added @snoyberg since he has contributed patches and bug reports in the past.

[snoyberg]

Thanks :)

[ezyang]

Added @NovaDenizen for #3657

[ezyang]

Added @0xmohit for #3660