Hi Gürkan,

Thank you for promptly updating the package and addressing the compatibility 
issues. I appreciate your initiative in labeling the revised package as version 
7.2.2.1. Typically, I adhere to a three-number versioning scheme for official 
releases. However, I understand the need for distinguishing this particular 
update, which primarily focuses on compatibility and minor fixes.

Regarding the version naming, I envisioned it more as a minor revision, like 
7.2.2-3, since the changes were essentially adjustments to ensure smooth 
compilation and operation on certain systems. Could you share your rationale 
for not adopting this versioning approach? It's crucial to maintain consistency 
in our versioning strategy to avoid confusion among users.

If there's any uncertainty, I encourage open communication. Please feel free to 
reach out to discuss. In special cases like this, we might consider making an 
exception and creating a release for 7.2.2.1. Nonetheless, it's also essential 
to consider the user's perspective – we want to prevent them from needing to 
re-download the software if the previous version functions adequately on their 
setup. Perhaps, we could limit this version to the upstream repository, 
reflecting the minor nature of the changes.

For clarity in the application's About section, the version number displayed 
can be easily adjusted. It's derived from the LazPaintVersion constant in the 
lazpainttype.pas file. To represent minor revisions like this, you could set it 
to something like "LazPaintVersion = 7020201;". This subtle modification allows 
us to manage minor updates efficiently, akin to using a dash version.

I'm grateful for your diligence in updating the package, especially for 
amending the email addresses. Your efforts ensure that the project remains 
current and accessible.

Regards,

-- 
  Johann ELSASS aka Juliette
  circu...@fastmail.com

On Mon, Jan 22, 2024, at 12:46 PM, Gürkan Myczko wrote:
> Hi Johan
>
>> Indeed, Lucas, the new version of Lazarus breaks existing code. There 
>> are some adjustments to do.
>> 
>> Gürkan, I have made the following adjustments in my upstream 
>> repository.
>> Location: https://github.com/bgrabitmap/lazpaint-upstream
>
> I have downloaded that version and called it 7.2.2.1, I hope that's 
> fine.
> It builds, it works. Closed the bug with upload...
>
>> Here are the changes:
>> - runtime fix for Qt (and in particular NixOS)
>> - compilation fix for Lazarus 3.0
>> - removed the debian folder (it was lagging behind the Debian 
>> repository)
>
> That's great. You should have tagged the new version on github.com, 
> sorry for
> the 7.2.2.1 version, the about still says 7.2.2
>
>> I presume the Debian repository is the one used to build.
>> Location: https://sources.debian.org/src/lazpaint/7.2.2-2/
>> 
>> I've noted that the copyright file has my old e-mail 
>> circu...@operamail.com. I suggest to update it to 
>> circu...@fastmail.com. There are three occurrences:
>> Upstream-Contact: Johann ELSASS <circu...@fastmail.com>
>> Copyright: 2011-2022 Johann ELSASS <circu...@fastmail.com>
>> Copyright: 2011-2022 Johann ELSASS <circu...@fastmail.com>
>
> I have updated all your email addresses.
>
> Regards,
>
>> Regards,
>> 
>> --
>>   Johann ELSASS aka Juliette
>>   circu...@fastmail.com

Reply via email to