https://builds.apache.org/job/maven-jenkinsfile/job/MNG-6117/ build in progress... let's see how it does
On 10 January 2017 at 22:01, Guillaume Boué <gb...@apache.org> wrote: > I created the branch for MNG-6117 with commit: > https://git1-us-west.apache.org/repos/asf?p=maven.git;a=comm > it;h=bd98ae6a3de8d443f5b3d2f895f2348c2912ae05 > > I will merge the branch into master on Monday the 16th if there are no > objections. > > Thanks, > Guillaume > > > Le 09/01/2017 à 12:06, Stephen Connolly a écrit : > >> OK, I have updated the versions in JIRA. >> >> Issues which have been agreed in the Big Scrub thread as being accepted >> for >> 3.5.0 are all now marked with FixVersion = 3.5.0 >> >> Issues which have been proposed for 3.5.0 but have not yet been agreed for >> 3.5.0 are now all marked with FixVersion = 3.5.0-candidate >> >> Please do not mark any issue with a FixVersion of 3.5.0 until we have had >> agreement to put it in scope. It is ok to move things to 3.5.0-candidate >> >> We need to start closing out the decisions on the 3.5.0-candidates. >> >> Also as release manager for 3.5.0 I am requesting that all changes for >> master must have a clean build on the full test suite before being merged >> to master (I would appreciate a heads up too) >> >> My expectation is that if you committed the changes towards 3.4.0, then >> you >> are responsible for tidying up the commits and preparing a branch for >> merging. >> >> -Stephen >> >> > > --- > L'absence de virus dans ce courrier électronique a été vérifiée par le > logiciel antivirus Avast. > https://www.avast.com/antivirus > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
