Am 04.03.22 um 17:13 schrieb Robert Clausecker:
I've now started working on the packaging.
Great!
Could you tell me which git commit your prerelease is based on? I need
something to work off.
I noticed that your master branch is still on a 2021-12-15 state and
development seems to be
happening on the associated_alpha branch. Which branch or commit should
I use for the packaging?
Ideally you could tag a prerelease so I can directly work off that.
I apologize for the moving target. I found a few bugs in the pre-release
version I offered in binary form which I have ironed out in the last few
days, and just now I have pushed a commit which is - hopefully - good:
https://bitbucket.org/kfj/pv/commits/a7e0d3a039766cb3b3651e672211ad9729b563c3?at=associated_alpha
or, a7e0d3a in short.
I have also set an annotated tag: 1.1.0-pre-2
I hope this is what you need for your packaging effort.
I now intend to consolidate the code - I have the feature level I want
for 1.1.0, but I'd like to have the code in use for some time to see if
more bugs crop up. Once I'm confident that all is well, I'll merge the
associated_alpha branch back into master and release 1.1.0.
Normally I work straight to the master branch, but with the move to
associated-alpha processing I was not sure my ideas would actually work
out, so I left the master branch at some 'safe' state. Luckily, so far,
it seems that the move worked as intended, and this made it possible to
add source image masking and stacking using the new code.
Kay
--
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
---
You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/hugin-ptx/9b55d118-8171-d7ff-5bc8-e50839b4e5b5%40yahoo.com.
