With 7 +1s (5 of which PMC), the vote passes.
Thanks everyone!
On Wed, Nov 29, 2023, at 6:40 PM, Francisco Guerrero wrote:
> +1
>
> On 2023/11/29 11:14:29 Alex Petrov wrote:
> > Even though we would like to bring harry in-tree, this is not an immediate
> > priority. Meanwhile, we need to
+1
On 2023/11/29 11:14:29 Alex Petrov wrote:
> Even though we would like to bring harry in-tree, this is not an immediate
> priority. Meanwhile, we need to unblock RPM builds for trunk, which means no
> custom jars. We will have at least one more Harry release with outstanding
> features to
+1
On Wed, Nov 29, 2023, at 7:03 AM, Brandon Williams wrote:
> +1
>
> Kind Regards,
> Brandon
>
> On Wed, Nov 29, 2023 at 5:15 AM Alex Petrov wrote:
> >
> > Even though we would like to bring harry in-tree, this is not an immediate
> > priority. Meanwhile, we need to unblock RPM builds for
+1
Kind Regards,
Brandon
On Wed, Nov 29, 2023 at 5:15 AM Alex Petrov wrote:
>
> Even though we would like to bring harry in-tree, this is not an immediate
> priority. Meanwhile, we need to unblock RPM builds for trunk, which means no
> custom jars. We will have at least one more Harry release
+1
> On 29 Nov 2023, at 11:35, Sam Tunnicliffe wrote:
>
> +1
>
>> On 29 Nov 2023, at 11:14, Alex Petrov wrote:
>>
>> Even though we would like to bring harry in-tree, this is not an immediate
>> priority. Meanwhile, we need to unblock RPM builds for trunk, which means no
>> custom jars. We
+1
> On 29 Nov 2023, at 11:14, Alex Petrov wrote:
>
> Even though we would like to bring harry in-tree, this is not an immediate
> priority. Meanwhile, we need to unblock RPM builds for trunk, which means no
> custom jars. We will have at least one more Harry release with outstanding
>
+1
On Wed, Nov 29, 2023 at 12:14:29PM +0100, Alex Petrov wrote:
> Even though we would like to bring harry in-tree, this is not an immediate
> priority. Meanwhile, we need to unblock RPM builds for trunk, which means no
> custom jars. We will have at least one more Harry release with
