Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipselink-dev] Development Process

On 21.11.14 22:21, Rick Curtis wrote:
> An accepted set of regression tests for the whole project must pass
What is the accepted set of regression tests that needs to be run?
Hi Rick,
I wouldn't go any further in the definition than to say it's the one which the commiter and reviewer agree is sufficient to cover potential impact of the tested changeset.

It does not make much sense to run MOXy tests for JPA change, e.g., some changes are naturally more risky and would deserve better upfront coverage, some are trivial or simple enough to be covered by sanity tests.

 MartiNG

On Wed, Nov 19, 2014 at 9:45 AM, Martin Grebac <martin.grebac@xxxxxxxxxx <mailto:martin.grebac@xxxxxxxxxx>> wrote:

    Hi devs,
     I've been updating some of the EL wikis recently, and revamped
    also the Development Process wiki at [1].Commiters please read
    through, refresh your memory and workflow ;O) (we should be all
    following what is written there, and what is written there should
    reflect what we do), and let me know if there are any comments,
    objections or suggestions.

     Cheers,
      MartiNG

    [1] https://wiki.eclipse.org/EclipseLink/Development/Process
    _______________________________________________
    eclipselink-dev mailing list
    eclipselink-dev@xxxxxxxxxxx <mailto:eclipselink-dev@xxxxxxxxxxx>
    To change your delivery options, retrieve your password, or
    unsubscribe from this list, visit
    https://dev.eclipse.org/mailman/listinfo/eclipselink-dev


--
*Rick Curtis*


_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev

--
Martin Grebac, SW Engineering Manager
Oracle Czech, Prague



Back to the top