Suggesting that the merge to master occur when a JEP is finalized

[jglick]

#12 apparently never said if or when a jep-nnnn feature branch would be merged into master. I am picking finalization time as a first pass, though it might make more sense to put it in master as soon as it is accepted.

(Frankly I was a little surprising to find that the merge to master does not happen as soon as the draft is accepted. That is after all the point at which you are committed to a particular number, so as a record of this JEP’s existence and status IMO it should be there already, even if it was ultimately rejected or abandoned.)

[bitwiseman]

@jglick
You are correct about wanting JEPs to be recorded even if rejected. But I also think we don't want to merge to master while in draft, since as you've seen, they may got through a lot of changes. Having all that iterating off to the side seems better to me.

Maybe take a few minutes and propose what you think it really should look like and then other can counter-propose/amend?

[jglick]

I also think we don't want to merge to master while in draft, since as you've seen, they may got through a lot of changes.

And…so? Is there some problem with having lots of PRs filed against the master branch? Who cares?

[jglick]

propose what you think it really should look like

#29

[bitwiseman]

@jglick Closing this in favor of #29.