Community
Participate
Working Groups
We'll use this bug to track the release We require IP Team approval of the IP Log. We require PMC approval of the release and review materials. There's help regarding releases in the handbook. https://www.eclipse.org/projects/handbook/#release
The next available review slot is January 15/2020 (we schedule reviews by end date). Please change your release date for that date or some number of days thereafter. There's more information in the handbook [1]. The project license shows EPL-1.0. We need this to be updated to EPL-2.0. Is this possible to complete before the release date? If not, please make it a priority for your next release. The CONTRIBUTING file in iottestware.coap contains a link that results in a 404. So does the README. I only checked a couple of your repositories; please fix them all (so that potential contributors will have a fighting chance). The "Edit on GitHub" link on your documentation page [3] results in a 404 as well. The Installation steps on this page start by cloning https://github.com/eclipse/iottestware.dashboard which appears to contain only a LICENSE file. The install script refers to a directory named "./TITAN". I don't see where this directory is created. What is it and what do you expect to find in there? The copyright statement on the documentation pages, "Copyright 2018, Eclipse IoT-Testware" aren't correct (Eclipse IoT-Testware is not a legal entity). Maybe change this to "Eclipse IoT-Testware contributors". [1] https://www.eclipse.org/projects/handbook/#release-review [2] https://github.com/eclipse/iottestware/blob/master/CONTRIBUTING.MD [3] https://iottestware.readthedocs.io/en/latest/quickstart_guide.html
The IP Log is approved. I need a response, please to Comment #1, and PMC Approval, please. (for the PMC approval, click on the "Send Email to PMC" link in the Committer Tools block on the release page [1]. [1] https://projects.eclipse.org/projects/technology.iottestware/releases/0.1.0
PMC Approval: https://www.eclipse.org/lists/technology-pmc/msg11553.html I've marked the review successful. Please continue with your release.
With the help of Jenkins, I build an uploaded a version of the release [1]. What are the next steps now? [1] https://download.eclipse.org/iottestware/snapshots/release-0.1.0/
(In reply to Sascha Kretzschmann from comment #4) > With the help of Jenkins, I build an uploaded a version of the release [1]. > What are the next steps now? > > [1] https://download.eclipse.org/iottestware/snapshots/release-0.1.0/ Disseminate to your community. Most projects create a download page on their project website or integrate it into their documentation. The specifics of how to do this are not included in the process, as we assume that you know the best way to deliver content to your community. Based on your documentation, straight downloads don't appear to be a natural way for your community to consume content. Note that there is no strict requirement that the project must provide downloads, only that if you do provide downloadable builds that you use download.eclipse.org. Are you providing this as docker containers?
Thanks, that helps a lot. Yes, a docker image is preferably.
(In reply to Sascha Kretzschmann from comment #6) > Thanks, that helps a lot. > > Yes, a docker image is preferably. You should make it as easy as possible to consume the project. Docker is a great way to make that happen. Please also make it as easy as possible for adopters to build from source. I don't see any response to my Comment 1. In particular, the "Edit on GitHub" link still gives me a 404. > The "Edit on GitHub" link on your documentation page [3] results in a 404 as > well. The Installation steps on this page start by cloning > https://github.com/eclipse/iottestware.dashboard which appears to contain > only a LICENSE file. Please address this and the other things that I highlighted ASAP.
Sorry, the link is obsolete and is now inactive. The up-to-date link: https://iottestware.readthedocs.io/en/master/index.html
(In reply to Sascha Kretzschmann from comment #8) > Sorry, the link is obsolete and is now inactive. Great. (In reply to Wayne Beaton from comment #7) > Please address this and the other things that I highlighted ASAP. You missed a couple of things... (In reply to Wayne Beaton from comment #1) > The project license shows EPL-1.0. We need this to be updated to EPL-2.0. Is > this possible to complete before the release date? If not, please make it a > priority for your next release. I need a response, please. > The CONTRIBUTING file in iottestware.coap contains a link that results in a > 404. So does the README. I only checked a couple of your repositories; > please fix them all (so that potential contributors will have a fighting > chance). Still there.
We'll take another run at resolving the outstanding issues with the next release review. Note that you'll need to engage in a new release review following the January 28 anniversary of this review.
