divmod-users team mailing list archive

[Tristan Seligmann <mithrandi@xxxxxxxxxxxxx>]

On Sat, Aug 3, 2013 at 12:10 PM, Laurens Van Houtven <_@xxxxxx> wrote:

> On Sat, Aug 3, 2013 at 12:22 AM, Tristan Seligmann <
> mithrandi@xxxxxxxxxxxxx> wrote:
>
>> On Fri, Aug 2, 2013 at 6:45 PM, Laurens Van Houtven <_@xxxxxx> wrote:
>>
>>> 1. Consensus and possibly feedback ("+1 do it" counts)
>>>
>>
>> +1, and thanks for the doing this! :)
>>
>> I have one addition to make to the release procedure: there should be a
>> merge proposal created for the release branch on Launchpad, even if you are
>> not having another person review the branch, as without the merge proposal
>> Launchpad will not associate the merge with the branch it merged.
>>
>
> Huh? I don't understand. Which merge with which branch? IIUC my proposal
> just involves a commit on trunk. How should I do it instead and why is this
> important?
>

Hmm, sorry, I think I just misread your steps because I was expecting
something there that wasn't. Normally any commit to trunk is the result of
merging some other branch, including releases, but I see now that you were
talking about a direct commit to trunk that doesn't involve any branches,
so the things I said about merge proposals are irrelevant in that light.

There are some reasons to prefer doing the release from a branch; for
example, you can roll tarballs / run CI / etc. without worrying about
somebody merging something to trunk in the time between when you start with
the release work, and when you commit the release; on the other hand, given
the frequency of trunk commits at this point in time, that's not
necessarily a significant concern at the moment.

>
>
>> As a separate suggestion, I think it might make compiling the release
>> notes easier if we adopted Twisted's "news fragment" system for providing
>> release notes text for each branch, but of course this requires a bit of
>> work to integrate.
>>
>
> That's a good idea, but something we can probably only start doing at the
> earliest after this release. As JP hinted ("assuming it actually works"),
> the best way to find that out is for me to actually try and roll a release
> ;)
>

Yeah, that definitely shouldn't be a release blocker, more of a "we should
look at doing this thing to make the next release easier".
-- 
mithrandi, i Ainil en-Balandor, a faer Ambar