On Thu, Feb 8, 2018 at 12:35 AM, Allan Haldane wrote:
> On 02/07/2018 04:26 PM, Charles R Harris wrote:
>> Hi All,
>>
>> I was thinking about things to do to simplify the NumPy development
>> process. One thing that came to mind was our use of prefixes on commits,
>> BUG, TST, etc. Those prefixes
On 02/07/2018 04:26 PM, Charles R Harris wrote:
> Hi All,
>
> I was thinking about things to do to simplify the NumPy development
> process. One thing that came to mind was our use of prefixes on commits,
> BUG, TST, etc. Those prefixes were originally introduced by David
> Cournapeau when he was
On Wed, 07 Feb 2018 14:26:37 -0700, Charles R Harris wrote:
> I was thinking about things to do to simplify the NumPy development
> process. One thing that came to mind was our use of prefixes on commits,
> BUG, TST, etc. Those prefixes were originally introduced by David
> Cournapeau when he was m
Other factors hindering new contributors:
1) Being unfamiliar with git. e.g. knowing that you have to fork numpy
first, then clone from your fork, then create a feature branch. That's just
the """straightforward bit""". It's hell the first time you have to rebase
something/correct commit messages/
I think that makes sense. Incidentally, I had imitated numpy's abbreviated
prefixes on various other projects until it was recently pointed out to me that
abbreviations, especially more cryptic ones like "ENH", "REF", and "MNT", are a
particularly tricky "hoop" to jump through for non-native spe
Hi All,
I was thinking about things to do to simplify the NumPy development
process. One thing that came to mind was our use of prefixes on commits,
BUG, TST, etc. Those prefixes were originally introduced by David
Cournapeau when he was managing releases in order help him track commits
that might
