divmod-users team mailing list archive
-
divmod-users team
-
Mailing list archive
-
Message #00034
Re: Release procedure for Divmod projects
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?
> 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
;)
cheers
lvh
Follow ups
References