On Wed, 2019-06-12 at 17:34 -0700, Nathaniel Smith wrote:
> On Wed, Jun 12, 2019 at 12:58 PM Marten van Kerkwijk
> wrote:
> > Overall, in favour of splitting the large files, but I don't like
> > that the notes stop being under version control (e.g., a follow-up
> > PR slightly changes things,
The attrs like you sent definitely sounded like it would translate to numpy
nearly trivially. I'm very much in favour!
-- Marten
___
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion
On Wed, Jun 12, 2019 at 12:58 PM Marten van Kerkwijk
wrote:
>
> Overall, in favour of splitting the large files, but I don't like that the
> notes stop being under version control (e.g., a follow-up PR slightly changes
> things, how does the note gets edited/reverted?).
>
> Has there been any
On Wed, 12 Jun 2019 15:57:48 -0400, Marten van Kerkwijk wrote:
> Overall, in favour of splitting the large files, but I don't like that the
> notes stop being under version control (e.g., a follow-up PR slightly
> changes things, how does the note gets edited/reverted?).
>
> Has there been any
Overall, in favour of splitting the large files, but I don't like that the
notes stop being under version control (e.g., a follow-up PR slightly
changes things, how does the note gets edited/reverted?).
Has there been any discussion of having, e.g., a directory
`docs/1.17.0-notes/`, and everyone
On Wed, 2019-06-12 at 11:45 -0700, Nathaniel Smith wrote:
> It might be worth considering a tool like 'towncrier'. It's
> automation to support the workflow where PRs that make changes also
> include their release notes, so when the release comes you've already
> done all the work and just have to
It's worth linking to the issue where this discussion started, so we avoid
repeating ourselves -
https://github.com/numpy/numpy/issues/13707.
Eric
On Wed, Jun 12, 2019, 11:51 Nathaniel Smith wrote:
> It might be worth considering a tool like 'towncrier'. It's automation to
> support the
It might be worth considering a tool like 'towncrier'. It's automation to
support the workflow where PRs that make changes also include their release
notes, so when the release comes you've already done all the work and just
have to hit the button.
On Wed, Jun 12, 2019, 07:59 Sebastian Berg
> 3. After merging, the release notes are copied into the wiki by the
> user or a contributor. After the copy happened, the label could/should
> be removed?
In astropy we keep our "whats-new-needed" label around, so people
doing the release can double check that everything is indeed ended up
in
On Wed, Jun 12, 2019 at 8:59 AM Sebastian Berg
wrote:
> Hi all,
>
> we had discussed trying a new strategy to gather release notes on the
> last community call, but not followed up on it on the list yet.
>
> For the next release, we decided to try a strategy of using a wiki page
> to gather
On Wed, Jun 12, 2019 at 4:59 PM Sebastian Berg
wrote:
> Hi all,
>
> we had discussed trying a new strategy to gather release notes on the
> last community call, but not followed up on it on the list yet.
>
> For the next release, we decided to try a strategy of using a wiki page
> to gather
Hi all,
we had discussed trying a new strategy to gather release notes on the
last community call, but not followed up on it on the list yet.
For the next release, we decided to try a strategy of using a wiki page
to gather release notes. The main purpose for this is to avoid merge
conflicts in
12 matches
Mail list logo
