I am also for a new bugfix release. As the master branch does not contain many new features, but it contains many more bugfixes then the bugfixes that went into 1.0.0 branch, I would suggest to not add new features into the master branch for about one or two weeks, but go through gerrit and apply the patches fixing only bugs to the master branch. After that create a new branch + RC release and start official QA testing.
Having a bugfix release would be nice there are a number of bugfixes already in the master branch or waiting in gerrit. Hauke -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Thiago Macieira Sent: Donnerstag, 12. November 2015 18:19 To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] IoTivity 1.0 patches On Thursday 12 November 2015 05:40:45 Markus Jung wrote: > Dear IoTivity maintainers, > as there has been a request to provide patches for the IoTivity 1.0 > release, I would like to ask to please report any know issues in Jira > and if patches are created also to merge them to the IoTivity 1.0.0 > release branch. Please also provide your opinion if you think a patch > release is required or the issues could be fixed with the next minor > feature release. Thanks, Best regards The patches should go into the 1.0 branch, not 1.0.0-dev. The latter was the branch we used to stabilise the 1.0.0 release and, now that that's done, the branch should be deleted. Instead, let's create a 1.0-dev branch for developing the 1.0.x patch releases. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
