[Pkg-emacsen-addons] wc-mode (and two pkg-emacsen questions)

[Nicholas D Steeves]

Dear Sean,

On 25 April 2017 at 17:09, Sean Whitton <spwhitton at spwhitton.name> wrote:
> Dear Nick,
>
> On Tue, Apr 25, 2017 at 04:06:50PM -0400, Nicholas Steeves wrote:
>> From what I've read about the freeze policy it cannot be unblocked.  Given
>> this, I'd like to maintain the stretch-bpo along packages I'm working on
>> for stretch+1 as part of my mini project.  I know it's early, but is there
>> such things as ITMB (intent to maintain backport)?
>
> You don't need to.  Just backport it when the time comes, or ask me to
> backport it.
>
>> Also, how should packages that must be uploaded to experimental during
>> a freeze be pushed to pkg-emacsen?  I'm guessing that I should
>> initially push my work as changelog UNRELEASED...  Then, should
>> master's changelog maintain an UNRELEASED distribution and should
>> experimental have it's own temporary branch?  Or maybe the
>> experimental branch should merge from master, dch -r -D experimental,
>> commit, build, tag, and then only the tag is pushed?  For that to
>> work, should the version be changed from 1.0-1 to something like
>> 1.0-1~experimental?  Based on
>> https://release.debian.org/stretch/freeze_policy.html I'm unclear if
>> elpafied packages can still be uploaded to unstable, so I'm assuming
>> experimental.  Please let me know if this isn't the case.
>
> If it's NEW, it can still go into unstable.

Thank you for the clarification!  I'm relieved to hear these cases are
simpler than I had anticipated.

Cheers,
Nicholas