I’m going to try a modified workflow this time in an attempt to eliminate the
duplicate testing effort that occurred between the “release branch” testing
during DISCUSS and the
subsequent staged RC validation that occurred during VOTE. Perform the testing
on the staged RC now and you will not have to perform that again as part of the
RC VOTE.
Release branch master:release-1.1.0 has been created and release candidate
1.1.0-incubating-RC1 has been created, tagged and staged [4].
Immediately raise any issues on this thread for discussion. That includes
lobbying for any additional JIRAs that should really be addressed in this
release.
If no issues are raised within 72 hours, a VOTE for the RC will be called.
See “Testing the Release” in the RM Guide [2] for what needs to be performed.
Volunteers are needed for the following items. Please help out and take
ownership of a JIRA. Thanks in advance!
EDGENT-348 Test the Console - the RM guide describes what’s needed.
EDGENT-349 Test Android
[1] process guide
https://cwiki.apache.org/confluence/display/EDGENT/A+guide+to+the+Apache+Edgent+release+process
[2] RM guide
https://cwiki.apache.org/confluence/display/EDGENT/Release+Manager's+Guide
[3] release process tracking https://issues.apache.org/jira/browse/EDGENT-334
[4] staged RC area https://dist.apache.org/repos/dist/dev/incubator/edgent/
