Missing tag for new version (3.0.9)

[remicollet]

Version 3.0.9 is released on pecl
but there is no tag here (latest is 3.0.5)

For context, I'm working on downstream packaging (RPM) and we are working on dropping pecl dependency, so pulling sources from git instead of pecl (pie is also on our radar, using packagist when possible)

[andrewdalpino]

Hi @remicollet,

The releases here on GitHub are for the Polyfill version of Tensor not the extension. The current version of Tensor PHP is 3.0.5 and the current version of Tensor Extension is 3.0.9.

Perhaps we'll have to unify the releases even though there may not be any new changes in one of them. Is there a better way to go about it in your experience?

Thanks, take care!

[remicollet]

Perhaps we'll have to unify the releases even though there may not be any new changes in one of them.

Make sense, as you choose a single repo for 2 projects

Notice: I think this will create a problem if you want to publish the extension AND the library on packagist, because you have a single composer.json

Perhaps you need to create a separate repo for the extension, with its own version schema, and easier to publish on packagist (ex rubix/tensor and rubix/ext-tensor)

Ex, see

• https://packagist.org/packages/maxmind-db/reader the library
• https://packagist.org/packages/maxmind-db/reader-ext the extension

[andrewdalpino]

Have you heard of monorepos? They are a type of repository that contain multiple projects. They are quite common in software development.

https://en.wikipedia.org/wiki/Monorepo

In this case, the benefit of combining the repos is the sharing of the testing suite. The same tests apply to both the extension and the Polyfill. When tests are improved for one project they are improved for both - and so there are benefits to maintaining this structure.

Ideally we'd like to maintain this benefit.

[remicollet]

Can you please fix the missing tags ?

[andrewdalpino]

Hi @remicollet let me see what I can do. What is it for? The PHP will be the same for each tag.

[remicollet]

3.0.10 is released... but things are really inconsistent

The content in pecl archive of 3.0.10 is really different from github content for tag 3.0.10
The extension is even set to 3.0.11 in the 3.0.10 tag

Attached the diff between pecl archive and githgub archive (ext directory)

diff.txt

[andrewdalpino]

That's right @remicollet, we do not tag PECL releases on GitHub.

If there is something special that you require, just spell it out and I'll try to accomodate you.

Is it that you need them synchronized? If that's all I can probable take care of that in the next bugfix release I'm working on.

[andrewdalpino]

Ok this latest release was in lockstep with PECL, the code should be the same.

https://github.com/RubixML/Tensor/releases/tag/3.0.11

[remicollet]

That's right @remicollet, we do not tag PECL releases on GitHub.

Please explain how to install the extension from git ?

Again, pecl is deprecated.

For nearly all extensions, I was able to switch the build for my repo from pecl archive to git snapshot.

PECL archive for 3.0.11 is not the same content than git tag (config.w32)
PECL archive for 3.1.0 is not the same content than git tag (config.w32, php_tensor.h, tensor/columnvector.zep.c...)

So the simplest solution for me is to stop providing this extension in my repository.

[andrewdalpino]

Here's instructions on how to compile the extension manually. You can use git to clone the repo, but git itself is not a compiler.

https://github.com/RubixML/Tensor#manually-compiling-the-extension

I'm not sure why the files are different, they were the same when they were tagged. Could it be that either pear or PECL changes the files?

Rather than force me to guess what your needs are, it would be much more helpful for you to just communicate them. So far you've just been pointing out random things but you are not connecting it to why that matters for your endeavor. I cannot help you if I don't understand what your problem is.