one thing we need: common focus for some time
there are so many directions followed by so many people at the same time that
nobody can't follow everything. And when it's about having Maven core evolve,
this is critical to have many people review and evaluate (it's less critical
for a plugin or
ok
there is only one additional point: when things were working previously
because of special cases that were handled with specific code previously, the
change has to be done with extra care: that's where the general intent of
fixing things has the immediate opposite effect
Then always we caref
Am 03/20/17 um 01:47 schrieb Christian Schulte:
> Am 03/20/17 um 01:11 schrieb Stephen Connolly:
>> On Sun 19 Mar 2017 at 12:13, Stephen Connolly <
>> stephen.alan.conno...@gmail.com> wrote:
>>
>>> We need to define:
>>>
>>> * what is a bug vs what is an rfe
>>>
>>> * what are the different severit
Am 03/20/17 um 01:11 schrieb Stephen Connolly:
> On Sun 19 Mar 2017 at 12:13, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
>> We need to define:
>>
>> * what is a bug vs what is an rfe
>>
>> * what are the different severities for bugs and rfes
>>
>
> S1: software is unusable, h
On Sun 19 Mar 2017 at 12:13, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> We need to define:
>
> * what is a bug vs what is an rfe
>
> * what are the different severities for bugs and rfes
>
S1: software is unusable, halts, crashes, or is inaccessible, resulting in
a critical impa
Am 03/19/17 um 23:32 schrieb Hervé BOUTEMY:
> for you, documentation is always right?
> That's the first time I see that documentation is more important and always
> more accurate than how the tool works
>
> If there is a discrepency between how the tool works and what is written in
> documentat
for you, documentation is always right?
That's the first time I see that documentation is more important and always
more accurate than how the tool works
If there is a discrepency between how the tool works and what is written in
documentation, there is work to be done to define what part has to
Am 19.03.2017 um 13:13 schrieb Stephen Connolly:
> We need to define:
>
> * what is a bug vs what is an rfe
I'll give it a try. Everything not working as documented/specified is a
bug, when there is consensus the documentation/specification is stating
the intended/correct behaviour. The design do
Please let's keep this for the other thread I am trying to start off.
It's really related to how we work with branches and how we use CI
(But that is a more complex thread to kick off)
So let's keep this thread on topic please
On Sun 19 Mar 2017 at 15:59, Christian Schulte wrote:
> Am 19.03.2
Am 19.03.2017 um 13:13 schrieb Stephen Connolly:
> We need to define:
>
> * what is a bug vs what is an rfe
>
> * what are the different severities for bugs and rfes
>
> * what severity bugs block: an alpha, a beta, a full release
>
> * what do the different release types mean? (My take, alpha
10 matches
Mail list logo