Make 1.0.0 release

[kghbln]

Tracking issue for the 1.0.0 release.

• Release notes

• Finalize RELEASE NOTES
• Update "README.md"
• Update "composer.json"
• Update version number "extension.json"
• Create tag
• Add release to Wikidata
• Update homepage
• Announce via mail
• Do a release tweet on Twitter
• Run composer update on smw.o
• Update "LocalSettings.php"
• Start development of new version
  • Update "composer.json" (update dev alias)
  • Update "extension.json" (new alpha version)
• Add extension to <doc.s-mw.o> Include new extensions for doxygen docu generation semantic-mediawiki.org#8

[mwjames]

The release has to happen after SMW 3.1 due to things like SemanticMediaWiki/SemanticMediaWiki#3770.

[kghbln]

Thanks for the info.

[kghbln]

We need to update CI for the latest AR version, preferably beyond 1.1 due to #12 (comment)

[krabina]

AR 1.2 is out...

[mwjames]

Unlikely that release is going to happen in 2019 and there is likely tendency that I will change the way of how the data are stored which is, instead of polluting an entity with Approv* properties, they are going to be stored as separate subobject which the user can reach via `Approved revs.xxx` in a query.

…

On 12/2/19, Bernhard Krabina ***@***.***> wrote: AR 1.2 is out... -- You are receiving this because you commented. Reply to this email directly or view it on GitHub: #3 (comment)

[hexmode]

Till this happens, the readme should be updated to indicate that you should use dev-master (or another tag) instead of 1.0.

[revansx]

I don't understand how there can be a "dev-master" if it doesn't show up in the list of branches. What am I missing?

[hexmode]

See the documenation:

If you want Composer to check out a branch instead of a tag, you need to point it to the branch using the special dev-* prefix

[revansx]

hmm.. the github repo for SAR only shows 1 branch (master) and there are no tags.. i'm guessing composer pulls code from somewhere else and this repo here on github is partial mirror. or am I really missing something obvious?

[krabina]

No, I am quite certain, github is the primary repo for all of SMW extensions.

[hexmode]

hmm.. the github repo for SAR only shows 1 branch (master) and there are no tags.. i'm guessing composer pulls code from somewhere else and this repo here on github is partial mirror. or am I really missing something obvious?

Composer pulls code from the github (or gitlab, or gerrit...) repository. It retrieves meta-information (what packages are available and from where) from packagist.org.

You can see that the packagist entry for SAR does not list any versions except "dev-master / 0.1.x-dev" because there are, in fact, no tags on this repository.

The 0.1.x-dev comes from the composer.json file where it is specified as an alias for dev-master.

[revansx]

"specified as an alias" <-- thanks!