Ok [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 01:31 h [INFO] Finished at: 2017-12-03T15:52:39+01:00 [INFO] Final Memory: 27M/437M [INFO] ------------------------------------------------------------------------
The staging repo is closed and all internal pre-release checks were successful. The address of the staging repo is: https://repository.apache.org/content/repositories/orgapacheedgent-1002 The address of the source-release is: https://repository.apache.org/content/repositories/orgapacheedgent-1002/org/apache/edgent/edgent-parent/1.2.0/edgent-parent-1.2.0-source-release.tar.gz or: https://repository.apache.org/content/repositories/orgapacheedgent-1002/org/apache/edgent/edgent-parent/1.2.0/edgent-parent-1.2.0-source-release.zip So, I guess I’m finished staging the release candidate. Unfortunately, I don’t quite know what went into 1.2.0 from 1.1.0 besides the maven migration. Could someone please sum up the changes and I’ll start the VOTE and DISCUSS threads. Chris Am 30.11.17, 19:47 schrieb "Dale LaBossiere" <dml.apa...@gmail.com>: continue on! :-) My version grep’s in branch release/1.2 (has 1.2.0-SNAPSHOT) and develop (has 1.3.0-SNAPSHOT) look good and everything built fine on both branches. Thanks! — Dale > On Nov 29, 2017, at 2:11 PM, Christofer Dutz <christofer.d...@c-ware.de> wrote: > ... > So, I deleted the original 1.2 branch and created a new one. I copy+pasted the command in the documentation, to check if the documentation is correct, and it seems to have updated all poms correctly this time. > > Please check the current state of the repo and if all is ok, we can continue starting a release attempt.
