You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
up-spec contains the documentation and requirements for the protocol while up-core-api holds the protos that are also part of the specifocations however they were split into separate projects early on (do not recall the justifications).
Having the spec and code in different locations are making tagging releases more difficult not to mention they reference each other often.
The text was updated successfully, but these errors were encountered:
the following change takes the 1.5.7 release of up-core-api and merges it with up-spec so we can have better traceability with the spec and protos.
#88
@stevenhartley this is the right thing to do 👍
I would like to create a PR for #71 which adds the relevant UAttributes requirements/constraints to uattributes.adoc.
FMPOV it would make sense to create the PR towards the core-api-merge branch. Would you agree?
* Merge up-spec and up-core-api
the following change takes the 1.5.7 release of up-core-api and merges it with up-spec so we can have better traceability with the spec and protos.
#88
* Remove unnecessary legal documents and update gitignore
* Fix the links
* Fix whitespace issues
* fixes to the utwin and uprotocol_options protos
up-spec contains the documentation and requirements for the protocol while up-core-api holds the protos that are also part of the specifocations however they were split into separate projects early on (do not recall the justifications).
Having the spec and code in different locations are making tagging releases more difficult not to mention they reference each other often.
The text was updated successfully, but these errors were encountered: