1. Forum
  2. USENET
  3. muc.lists.freebsd.ports

  • =?UTF-8?Q?Re:_[PATCH]_databases/redisjson:_Upst?= =?UTF-8?Q?ream_status_change_=E2=80=94_seeking_guidance?=

    From wadegimpbc@wadegimpbc@tuta.com to muc.lists.freebsd.ports on Fri Mar 20 15:25:18 2026
    From Newsgroup: muc.lists.freebsd.ports

    ------=_Part_32539_158212298.1774016718127
    Content-Type: text/plain; charset=UTF-8
    Content-Transfer-Encoding: 7bit


    Robert,


    Following up on my maintainership request. While preparing the update, I found that upstream (RedisJSON/RedisJSON) now states "We no longer release standalone versions of RedisJSON." Starting with Redis 8, RedisJSON is bundled directly into the Redis server.


    The current port is at v2.0.8. The question is: what's the right path forward?

    Update to the last standalone release (2.6.x) for users on older Redis versions Mark the port as deprecated since the functionality is now in Redis 8
    Some other approach I'm not seeing as a newcomer

    I'd rather ask before submitting a patch that takes the wrong direction. What does the community prefer here?


    Wade Markham wadegimpbc@tuta.com




    ------=_Part_32539_158212298.1774016718127
    Content-Type: text/html; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable

    <html>
    <head>
    <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-8=

    </head>
    <body>
    <p class=3D"">Robert,<br></p><p class=3D"">Following up on my maintainershi=
    p request. While preparing the update, I found that upstream (RedisJSON/Red= isJSON) now states "We no longer release standalone versions of RedisJSON."=
    Starting with Redis 8, RedisJSON is bundled directly into the Redis server= .<br></p><p class=3D"">The current port is at v2.0.8. The question is: what=
    's the right path forward?<br></p><ol class=3D""><li class=3D"">Update to t=
    he last standalone release (2.6.x) for users on older Redis versions<br></l= i><li class=3D"">Mark the port as deprecated since the functionality is now=
    in Redis 8<br></li><li class=3D"">Some other approach I'm not seeing as a = newcomer<br></li></ol><p class=3D"">I'd rather ask before submitting a patc=
    h that takes the wrong direction. What does the community prefer here?<br><= /p><p class=3D"">Wade Markham <a class=3D"" href=3D"mailto:wadegimpbc@tuta.= com" rel=3D"noopener noreferrer" target=3D"_blank">wadegimpbc@tuta.com</a><= br></p><div dir=3D"auto"><br></div><div dir=3D"auto"><br></div> </body> </html>

    ------=_Part_32539_158212298.1774016718127--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From Ronald Klop@ronald-lists@klop.ws to muc.lists.freebsd.ports on Fri Mar 20 15:55:49 2026
    From Newsgroup: muc.lists.freebsd.ports

    ------=_Part_1436_87662023.1774018549102
    Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable

    I think somebody else was looking at the same port at the same time.

    https://cgit.freebsd.org/ports/commit/?id=3D77284f93863b4c143470faf6e36be61= 5e3c68723

    Regards,
    Ronald.

    =20
    Van: wadegimpbc@tuta.com
    Datum: vrijdag, 20 maart 2026 15:25
    Aan: Freebsd Ports <freebsd-ports@freebsd.org>
    CC: Robert Clausecker <fuz@freebsd.org>
    Onderwerp: Re: [PATCH] databases/redisjson: Upstream status change =E2=80=
    =94 seeking guidance
    =20
    Robert,
    =20
    Following up on my maintainership request. While preparing the update, I =
    found that upstream (RedisJSON/RedisJSON) now states "We no longer release = standalone versions of RedisJSON." Starting with Redis 8, RedisJSON is bund= led directly into the Redis server.
    =20
    The current port is at v2.0.8. The question is: what's the right path for=
    ward?
    =20
    Update to the last standalone release (2.6.x) for users on older Redis ve=
    rsions
    Mark the port as deprecated since the functionality is now in Redis 8
    Some other approach I'm not seeing as a newcomer
    I'd rather ask before submitting a patch that takes the wrong direction. =
    What does the community prefer here?
    =20
    Wade Markham wadegimpbc@tuta.com
    =20
    =20
    =20

    =20
    ------=_Part_1436_87662023.1774018549102
    Content-Type: text/html; charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    <html><head></head><body>I think somebody else was looking at the same port=
    at the same time.<br>

    https://cgit.freebsd.org/ports/commit/?id=3D77284f93863b4c143470faf6e36be61= 5e3c68723<br>

    Regards,<br>
    Ronald.<br>

    &nbsp;
    <p><strong>Van:</strong> wadegimpbc@tuta.com<br>
    <strong>Datum:</strong> vrijdag, 20 maart 2026 15:25<br>
    <strong>Aan:</strong> Freebsd Ports &lt;freebsd-ports@freebsd.org&gt;<br> <strong>CC:</strong> Robert Clausecker &lt;fuz@freebsd.org&gt;<br> <strong>Onderwerp:</strong> Re: [PATCH] databases/redisjson: Upstream statu=
    s change =E2=80=94 seeking guidance</p>

    <blockquote style=3D"padding-right: 0px; padding-left: 5px; margin-left: 5p=
    x; border-left: #000000 2px solid; margin-right: 0px">
    <div class=3D"MessageRFC822Viewer" id=3D"P">
    <div class=3D"MultipartAlternativeViewer">
    <div class=3D"TextHTMLViewer" id=3D"P.P.P">
    <p>Robert,</p>

    <p>Following up on my maintainership request. While preparing the update, I=
    found that upstream (RedisJSON/RedisJSON) now states "We no longer release=
    standalone versions of RedisJSON." Starting with Redis 8, RedisJSON is bun= dled directly into the Redis server.</p>

    <p>The current port is at v2.0.8. The question is: what's the right path fo= rward?</p>


    =09<li>Update to the last standalone release (2.6.x) for users on older Red=
    is versions</li>
    =09<li>Mark the port as deprecated since the functionality is now in Redis = 8</li>
    =09<li>Some other approach I'm not seeing as a newcomer</li>
    </ol>

    <p>I'd rather ask before submitting a patch that takes the wrong direction.=
    What does the community prefer here?</p>

    <p>Wade Markham <a href=3D"mailto:wadegimpbc@tuta.com" target=3D"_blank">wa= degimpbc@tuta.com</a></p>

    <div>&nbsp;</div>

    <div>&nbsp;</div>
    </div>
    </div>
    </div>
    </blockquote>

    &nbsp;</body></html>
    ------=_Part_1436_87662023.1774018549102--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From Moin Rahman@bofh@freebsd.org to muc.lists.freebsd.ports on Fri Mar 20 16:15:16 2026
    From Newsgroup: muc.lists.freebsd.ports


    --Apple-Mail=_4C4C2D82-8548-44FE-9750-DBA611A660BB
    Content-Transfer-Encoding: quoted-printable
    Content-Type: text/plain;
    charset=utf-8

    I didn't see this mail but the Redis team reached out to me as I am
    maintaining redis*.

    Kind regards,
    Moin

    On Mar 20, 2026, at 15:55, Ronald Klop <ronald-lists@klop.ws> wrote:
    =20
    I think somebody else was looking at the same port at the same time.
    =20
    =
    https://cgit.freebsd.org/ports/commit/?id=3D77284f93863b4c143470faf6e36be6= 15e3c68723
    =20
    Regards,
    Ronald.
    =20
    Van: wadegimpbc@tuta.com
    Datum: vrijdag, 20 maart 2026 15:25
    Aan: Freebsd Ports <freebsd-ports@freebsd.org>
    CC: Robert Clausecker <fuz@freebsd.org>
    Onderwerp: Re: [PATCH] databases/redisjson: Upstream status change =E2=80=
    =94 seeking guidance
    Robert,
    Following up on my maintainership request. While preparing the update, =
    I found that upstream (RedisJSON/RedisJSON) now states "We no longer =
    release standalone versions of RedisJSON." Starting with Redis 8, =
    RedisJSON is bundled directly into the Redis server.
    The current port is at v2.0.8. The question is: what's the right path =
    forward?
    =E2=80=A2 Update to the last standalone release (2.6.x) for users =
    on older Redis versions
    =E2=80=A2 Mark the port as deprecated since the functionality is =
    now in Redis 8
    =E2=80=A2 Some other approach I'm not seeing as a newcomer
    I'd rather ask before submitting a patch that takes the wrong =
    direction. What does the community prefer here?
    Wade Markham wadegimpbc@tuta.com
    =20
    =20


    --Apple-Mail=_4C4C2D82-8548-44FE-9750-DBA611A660BB
    Content-Transfer-Encoding: 7bit
    Content-Disposition: attachment;
    filename=signature.asc
    Content-Type: application/pgp-signature;
    name=signature.asc
    Content-Description: Message signed with OpenPGP

    -----BEGIN PGP SIGNATURE-----

    iQKTBAEBCgB9FiEETfdREoUGjQZKBS+fvbm1phfAvJEFAmm9ZIRfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDRE Rjc1MTEyODUwNjhEMDY0QTA1MkY5RkJEQjlCNUE2MTdDMEJDOTEACgkQvbm1phfA vJG6yA/+KVwVHs+SVgEFUvGiuRwHCuiLkGlUJTJbfDNqKl3XGFTILaTN0X43YEZH YQDHd0ApLjR59ZzSj0ImE5h0nuCVId43S8dauZu12nCClhEUj5dDQAKjTiQBdroh PKcDmo0fP9/TDfPlY504rgzEn2uNK7tMrymKQn3hyc0qhzgB8uptLRSLN8SN8TBh 4fRHw+J6ROn17tlrH6MiJqqpbWr3aW/81IgnmZCkoyThxHlbqF3Y7Nowi6ZrCfrC JCHZhTEWi/Q+GWFhQ6HO+L9bIDRaEUMqxEM8sgPSpgW92q4KlXFgz1OnM2Gm6qQn QnDFFcN2lqdP0ZyDiivdNdH0R4OeUyFfFxQhOUdMoyXUPmrUSt+2PoJjwIzk0WHt XCDwiEMy+TEe86xHWORj17C1bULe9v7pEae5a+cXhdh2/tc+PHTA7RzCI5uGY2Ff +ccpgOXF7e7Gj16GqceBMkkMl7nd3rvWoyP/ngV5gnFc7y2H44yojVeT/mgFXzRY 0U1LH2E9LW7j+T9VojwoQCUjv1//FdY6DV2HWKTf/FKtfy/7nrJTJIgjRsqG+Wfn g4PAZ4sLQ6xtdGijpPQD5X5lqj6phF+Cv3NGN6vK8X/pt4FuWRquCu9Z4UQMMT/3 zZBPvr3NP1s0DU005qEQ/vIPs6Epn5dp4toqwRoPa/ef+oREKBU=
    =lNnU
    -----END PGP SIGNATURE-----

    --Apple-Mail=_4C4C2D82-8548-44FE-9750-DBA611A660BB--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From wadegimpbc@wadegimpbc@tuta.com to muc.lists.freebsd.ports on Fri Mar 20 16:40:10 2026
    From Newsgroup: muc.lists.freebsd.ports

    ------=_Part_10262_696446165.1774021210220
    Content-Type: text/plain; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable


    Moin, Robert, Ronald =E2=80=94


    Good timing all around. Glad to see the port landed in good hands.


    Robert, thank you for the process walkthrough. I'll follow that exact path = =E2=80=94 Bugzilla update with a patch =E2=80=94 on my next port. My Bugzil=
    la account is still pending activation (emailed bugmeister earlier this wee= k), so once that's live I'll be back with something substantive.


    Appreciate the welcome.


    Wade Markham wadegimpbc@tuta.com



    ------=_Part_10262_696446165.1774021210220
    Content-Type: text/html; charset=UTF-8
    Content-Transfer-Encoding: quoted-printable

    <html>
    <head>
    <meta http-equiv=3D"content-type" content=3D"text/html; charset=3DUTF-8=

    </head>
    <body>
    <p class=3D"">Moin, Robert, Ronald =E2=80=94<br></p><p class=3D"">Good timi=
    ng all around. Glad to see the port landed in good hands.<br></p><p class= =3D"">Robert, thank you for the process walkthrough. I'll follow that exact=
    path =E2=80=94 Bugzilla update with a patch =E2=80=94 on my next port. My = Bugzilla account is still pending activation (emailed bugmeister earlier th=
    is week), so once that's live I'll be back with something substantive.<br><= /p><p class=3D"">Appreciate the welcome.<br></p><p class=3D"">Wade Markham =
    <a class=3D"" href=3D"mailto:wadegimpbc@tuta.com" rel=3D"noopener noreferre=
    r" target=3D"_blank">wadegimpbc@tuta.com</a><br></p><div dir=3D"auto"><br><= /div> </body>
    </html>

    ------=_Part_10262_696446165.1774021210220--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21e-Linux NewsLink 1.2
  • From Moin Rahman@bofh@freebsd.org to muc.lists.freebsd.ports on Fri Mar 20 19:01:33 2026
    From Newsgroup: muc.lists.freebsd.ports


    --Apple-Mail=_9968C856-2372-42E8-A9B2-24BE3130E6A0
    Content-Transfer-Encoding: quoted-printable
    Content-Type: text/plain;
    charset=utf-8



    On Mar 20, 2026, at 16:40, wadegimpbc@tuta.com wrote:
    =20
    Moin, Robert, Ronald =E2=80=94
    Good timing all around. Glad to see the port landed in good hands.
    Robert, thank you for the process walkthrough. I'll follow that exact =
    path =E2=80=94 Bugzilla update with a patch =E2=80=94 on my next port. =
    My Bugzilla account is still pending activation (emailed bugmeister =
    earlier this week), so once that's live I'll be back with something = substantive.
    Appreciate the welcome.
    Wade Markham wadegimpbc@tuta.com
    =20

    I have created the account in Bugzilla.

    You can try to reset your password.

    Kind regards,
    Moin=

    --Apple-Mail=_9968C856-2372-42E8-A9B2-24BE3130E6A0
    Content-Transfer-Encoding: 7bit
    Content-Disposition: attachment;
    filename=signature.asc
    Content-Type: application/pgp-signature;
    name=signature.asc
    Content-Description: Message signed with OpenPGP

    -----BEGIN PGP SIGNATURE-----

    iQKTBAEBCgB9FiEETfdREoUGjQZKBS+fvbm1phfAvJEFAmm9i31fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDRE Rjc1MTEyODUwNjhEMDY0QTA1MkY5RkJEQjlCNUE2MTdDMEJDOTEACgkQvbm1phfA vJFyVg/9FV8kC2Z7OWnlwjOE9OV0gFP0NaTh24QajJe4xJ0Hv3Mz2ZMJ3mRxvMkk SePzXWumVn/ln28oTeLaF+2lYe3X20LPgusk5iplbw0Kfn2VIS3CCK98M0L4KiY+ v1CHJGV7DYJlC/e5B5sQ7v1KTxINqXJuZGAQPcdw6nbADlFIYNBAXJ7ptBR7d9xV DdwoMLO1nLry6PysHiCeekL4FGIHlLZlr58wiLvQPjoChGbkzDK5I9pRjWHxdRx3 Vj6yVxaXDIfo0PfNfGHSRp+fIkyOFqQlPbGXCIT6N7Uv1mzzlbbWcagCd7fMf80L K+RtkcpPX+pxjxiWnDyr3yG9ePpYbt0TsrzI8oPXZ6tBmb/dEYt7oGnlBaLfJPq/ zJKkvp5bEKDp6uLzDNGjbJJ/o4R9grIvGuvT25KkO1QH2Es8TIdm3w9yJNwOjyNp s9lz3LzvCMQbU70n0IL/oRKwsNiKdGsOUnVbFaMegP8lSOVFJ6/pVJJ5W5IDRzg8 4Zw68O0NroSGyFYiItufQVn8FpXLi2b5s8vygWW87q+3d3mUrxUg4MZz6mIdBlaZ 4bFk9G2ZCGYxx4a3yXYeikodg7a/JOkHfd2btTMYlwSswGdxxHpL5jeHvksDCtJZ UHZexq2bsey4B/CPac7jCh3DVfBJ4FcLg5+pjGmzlVWA4e+JrRI=
    =8d92
    -----END PGP SIGNATURE-----

    --Apple-Mail=_9968C856-2372-42E8-A9B2-24BE3130E6A0--


    --
    Posted automagically by a mail2news gateway at muc.de e.V.
    Please direct questions, flames, donations, etc. to news-admin@muc.de
    --- Synchronet 3.21e-Linux NewsLink 1.2