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 impact on the operation. No workaround is available Examples: Maven crashes on OS-X Maven goes into infinite loop when installing war artifacts S2: software operates but due to an error, its operation is severely restricted. No workaround is available Examples: Maven deploys invalid/corrupt artifacts Maven silently skips tests without asking Maven ignores batch mode and auto-version submosules for a reactor with more than 20 modules to release S3: software operates with limitations due to an error that is not critical to the overall operation. For example, a workaround forces a user to use a time-consuming procedure to operate the software, or removes a non-essential feature. Examples: Maven has started to prompt with Y/N for each test to be run when -DconfirmTests=false or when in batch mode. Maven is stuck logging at debug level S4: software can be used with only slight inconvenience. Examples: Maven colour logging is broken. Maven is prompting to start execution at the start of the reactor when not in batch mode Wdyt > * what severity bugs block: an alpha, a beta, a full release > > * what do the different release types mean? (My take, alpha is not feature > complete, beta is not free of bugs, rc is hopefully the real deal) > > * how do we decide when to bump major, minor and patch version numbers and > what scope of changes should be allowed in a non-patch bump > -- > Sent from my phone > -- Sent from my phone
