[SHOULD] Work towards fulfilling the requirements for a full GE about fiware-draco HOT 4 CLOSED

Hi @jason-fox,
Where can I find the links for QA Section about Draco?

from fiware-draco.

@anmunoz - I think that will have to wait for the QA team to test and release the results.

from fiware-draco.

Hi @jason-fox ,
I have been checking the requirements and I will answered with the modifications:

Missing Badges:

README Badge - CI Build/Unit Test (Travis)----(Pending)

Missing items within the README

README - QA Section (Included but TBD waiting for the QA team)
README - Training Section (Included but waiting for the tutorial in Fiware academy)
README - ToC ---- Done
README - How to Deploy text present --- Done
README - How to Run Tests text present----- Done
README - Main API Walkthrough text present-- Done
README - Access to the advanced API and Documentation text present--- Done

Missing Release Item

Releases uses SemVer (Please clarify I don't now what I have to do here)
(note the existing FIWARE_7.5 tag satisfies alignment for FIWARE releases)

Missing Docker Items

DOCKER - SemVer Image Available (Please clarify I don't now what I have to do here)
DOCKER - FIWARE Image Available (Please clarify I don't now what I have to do here)

No CREDITS file ----- Included and done

from fiware-draco.

README Badge - CI Build/Unit Test (Travis)----(Pending)

Its fine for an Incubated enabler to be pending items, they will need to be completed before applying for Full Member status.

README - QA Section (Included but TBD waiting for the QA team)
README - Training Section (Included but waiting for the tutorial in Fiware academy)

The QA section will fill automatically once the values are available. Personally I would have waited until they are available myself. For the training part, do you have slides or a video you could contribute to the Academy - if so just make a PR and/or raise an issue to get it included.

README - ToC ---- Done
README - How to Deploy text present --- Done
README - How to Run Tests text present----- Done
README - Main API Walkthrough text present-- Done
README - Access to the advanced API and Documentation text present--- Done

Great.

Releases uses SemVer (Please clarify I don't now what I have to do here)
(note the existing FIWARE_7.5 tag satisfies alignment for FIWARE releases)

Looking at the releases tab, you have one release called FIWARE_7.5 which is (actually just a tag under the hood) - this isn't a SemVer tag, its just a marker for the overall FIWARE release.A semantic release version would be major.minor.build - e.g. 1.0.0

All you need to do is to add another tag to 0c35a1d with the appropriate version number.
You can see an example here

DOCKER - SemVer Image Available (Please clarify I don't now what I have to do here)
DOCKER - FIWARE Image Available (Please clarify I don't now what I have to do here)

If you go to Docker Hub Draco is only offering the latest build, compare this with Keyrock which has tags for each FIWARE Release and each semver release.

You just need to checkout the code at 0c35a1d , build the versioned docker container and push to Docker Hub

docker build -t fiware-draco:FIWARE_7.5.1 .
docker login
docker push fiware-draco:FIWARE_7.5.1

and repeat for the semVer version.

from fiware-draco.