2009/12/29 Stephen Connolly <[email protected]> > > > 2009/12/29 Stephen Connolly <[email protected]> > >> Follow on from: >> http://old.nabble.com/What%27s-blocking-releasing-maven-compiler-plugin--td26154745.html#a26156747 >> >> >> Here is my proposal of the test plan. >> >> 1. We (=benjamin) set up the grid @ sonatype to use the >> maven-plugin-enforcer ( >> https://svn.apache.org/repos/asf/maven/sandbox/trunk/maven/maven-plugin-enforcer >> ) >> >> Done > > >> 2. We (=benjamin) run all the builds that are currently working with >> m3+plugin-enfocer+new compiler plugin -SNAPHOT. If all builds still pass >> with the new compiler plugin, then we say all is good >> >> > Done: > https://grid.sonatype.org/ci/job/maven-shared/jdk=1.5,label=ubuntu/178/console > > Question: what other jobs should we proof with before we hit step 3? >
Benjamin has run against: - archetype - m3 - scm - surefire - release - wagon - core-its - modello Unless anyone has any objections, I will push a release tomorrow. -Stephen > > >> 3. If all is good, we (=benjamin or me or somebody else) stage a release >> of maven-compiler plugin. >> >> 4. We (=benjamin) run all the builds that are currently working with >> m3+plugin-enfocer+new compiler plugin (staged release). If all builds still >> pass with the new compiler plugin, then we say all is good and call a vote >> >> Any body got any objections / additional test cases to add? >> >> -Stephen >> >> P.S. we should re-use this test plan for surefire >> > >
