search

SemanticMediaWiki / SemanticApprovedRevs

Complementary extension to Semantic MediaWiki and Approved Revs to control the storage of approved revision content
Other
4 stars 3 forks source link

Make 1.0.0 release #3

Open kghbln opened 5 years ago

kghbln commented 5 years ago

Tracking issue for the 1.0.0 release.

mwjames commented 5 years ago

The release has to happen after SMW 3.1 due to things like https://github.com/SemanticMediaWiki/SemanticMediaWiki/pull/3770.

kghbln commented 5 years ago

Thanks for the info.

kghbln commented 5 years ago

We need to update CI for the latest AR version, preferably beyond 1.1 due to https://github.com/SemanticMediaWiki/SemanticApprovedRevs/pull/12#issuecomment-516164689

krabina commented 4 years ago

AR 1.2 is out...

mwjames commented 4 years ago

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 notifications@github.com wrote:

AR 1.2 is out...

-- You are receiving this because you commented. Reply to this email directly or view it on GitHub: https://github.com/SemanticMediaWiki/SemanticApprovedRevs/issues/3#issuecomment-560369460

hexmode commented 4 years ago

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

revansx commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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 commented 4 years ago

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

hexmode commented 4 years ago

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 commented 4 years ago

"specified as an alias" <-- thanks!