Closed Potherca closed 2 years ago
I am in the process of implementing the changes for the PDS Migrator in our PHP code. There were some minor issues for which I'll open an MR.
I noticed we are a bit behind in creating a new release. The latest tag is v0.5.1 from November last year.
In the meantime, 117 commits have been made to main, mostly fixes from December to February. The same goes for pdsinterop/php-solid-auth#v0.6.1. Both pdsinterop/php-solid-crud#v0.3.0 and pdsinterop/flysystem-rdf#v0.3.0 are already up-to-date.
main
pdsinterop/php-solid-auth#v0.6.1
pdsinterop/php-solid-crud#v0.3.0
pdsinterop/flysystem-rdf#v0.3.0
I was thinking of tagging a new release as v0.6.0. I'd like to include a fix for #43 and #46 (as they are trivial to add).
v0.6.0
Any/All changes after that, for the Migrator, would then be tagged as v0.7.0.
v0.7.0
Better to leave that for later, that code is on proof-of-concept level at best and probably insecure.
I am in the process of implementing the changes for the PDS Migrator in our PHP code. There were some minor issues for which I'll open an MR.
I noticed we are a bit behind in creating a new release. The latest tag is v0.5.1 from November last year.
In the meantime, 117 commits have been made to
main
, mostly fixes from December to February. The same goes forpdsinterop/php-solid-auth#v0.6.1
. Bothpdsinterop/php-solid-crud#v0.3.0
andpdsinterop/flysystem-rdf#v0.3.0
are already up-to-date.I was thinking of tagging a new release as
v0.6.0
. I'd like to include a fix for #43 and #46 (as they are trivial to add).Any/All changes after that, for the Migrator, would then be tagged as
v0.7.0
.Questions