Vendor/Release Structure

Draft

Vendors that are building against Mer have usually multiple repositories, this document is an example how these repositories are formed and could be published.

= Repository names =

live
A repository where the real time development happens.

next
A repository that is snapshot of the next upcoming release from the vendor.

latest
Points to the latest static release.

= Content of repositories = Each repository needs to define the Mer release it was build against, HOW? File? Content of file? URL? Copied Mer release?

Example repository structure
/ releases/ / builds/ /             images/ next latest live