Groups > linux.debian.maint.python > #9951

Re: RFS: jupyter components

From	Diane Trout <diane@ghic.org>
Newsgroups	linux.debian.maint.python
Subject	Re: RFS: jupyter components
Date	2017-10-25 23:00 +0200
Message-ID	<uEAWl-4AA-5@gated-at.bofh.it> (permalink)
References	(1 earlier) <uByo2-1za-15@gated-at.bofh.it> <uBFSy-6X4-3@gated-at.bofh.it> <uEznz-3Om-1@gated-at.bofh.it> <uEA0h-41x-1@gated-at.bofh.it> <uEAtk-4qB-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Wed, 2017-10-25 at 22:15 +0200, Gordon Ball wrote:
> 
> I would normally not update the timestamp while the suite is
> UNRELEASED,
> and expect whoever ultimately makes the upload to `dch -r` and tag
> the
> release, but maybe it would be less ambiguous to update it each time
> d/changelog gets edited.

In my own packages I update the changelog timestamp when creating a new
release, and then one final update for release. I'm not sure there's
clearly a right answer in this case.

The thing that made me want to have one of you to update the changelog
was Section 4.4 of the debian policy which says:

The maintainer name and email address used in the changelog should be
the details of the person who prepared this release of the package.
They are not necessarily those of the uploader or usual package
maintainer. 

> 
> I think I have DM upload rights for jupyter-notebook but not the
> others
> listed.

I don't mind doing a review & uploading. But if you want to upload go
ahead

I just uploaded nbconvert instead of going around in email a couple
more times.

Diane

Thread

RFS: jupyter components Gordon Ball <gordon@chronitis.net> - 2017-08-29 00:50 +0200
  Re: RFS: jupyter components Julien Puydt <julien.puydt@laposte.net> - 2017-09-04 04:40 +0200
    Re: RFS: jupyter components Gordon Ball <gordon@chronitis.net> - 2017-09-04 10:50 +0200
      Re: RFS: jupyter components Julien Puydt <julien.puydt@laposte.net> - 2017-09-04 17:10 +0200
        Re: RFS: jupyter components Julien Puydt <julien.puydt@laposte.net> - 2017-09-04 18:20 +0200
          Re: RFS: jupyter components Julien Puydt <julien.puydt@laposte.net> - 2017-09-04 19:30 +0200
            Re: RFS: jupyter components Gordon Ball <gordon@chronitis.net> - 2017-09-04 19:50 +0200
  Re: RFS: jupyter components Julien Puydt <julien.puydt@laposte.net> - 2017-09-08 18:50 +0200
    Re: RFS: jupyter components Gordon Ball <gordon@chronitis.net> - 2017-10-13 01:00 +0200
  Re: RFS: jupyter components Adam Cecile <acecile@le-vert.net> - 2017-10-17 13:40 +0200
    Re: RFS: jupyter components Gordon Ball <gordon@chronitis.net> - 2017-10-17 21:40 +0200
      Re: RFS: jupyter components Diane Trout <diane@ghic.org> - 2017-10-25 21:20 +0200
        Re: RFS: jupyter components Julien Puydt <julien.puydt@laposte.net> - 2017-10-25 22:00 +0200
          Re: RFS: jupyter components Gordon Ball <gordon@chronitis.net> - 2017-10-25 22:30 +0200
            Re: RFS: jupyter components Diane Trout <diane@ghic.org> - 2017-10-25 23:00 +0200
            Re: RFS: jupyter components Diane Trout <diane@ghic.org> - 2017-10-25 23:40 +0200
            Re: RFS: jupyter components Diane Trout <diane@ghic.org> - 2017-10-26 00:10 +0200

csiph-web