Option 2, since it is already basically set up, seems like the appropriate
option, in my opinion.
BKP
Brian Proffitt
VP, Marketing & Publicity
VP, Conferences
On Thu, Aug 1, 2024 at 8:42 AM Justin Mclean
wrote:
> Hi,
>
> Given it is shared already, option 2 seems fine. It is version control,
Hi,
Given it is shared already, option 2 seems fine. It is version control, so any
issues, if they occur, should be able to be easily corrected.
Kind Regards,
Justin
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache
Thanks for the detailed breakdown of the issue.
Ideally option 3 if it is feasible to implement. I'm not against
option 2 as a short term solution to unblock KIE release.
On Thu, 1 Aug 2024 at 12:14, Alex Porcelli wrote:
>
> Thank you for the detailed information, Daniel!
>
> Although I'm not an
Thank you for the detailed information, Daniel!
Although I'm not an IPMC member, I'd like to express that option 3
looks almost like a no brainer :)
Looking forward to hearing from IPMC members.
On Thu, Aug 1, 2024 at 7:02 AM Daniel Gruno wrote:
>
> On 8/1/24 12:42, Alex Porcelli wrote:
> > Dea
On 8/1/24 12:42, Alex Porcelli wrote:
Dear IPMC members,
The KIE podling is preparing for its first Apache release. Due to the
numerous artifacts we build across various repositories (container
images, Java libraries, web apps, etc.), we seek to automate the SVN
upload as part of our release pro
Dear IPMC members,
The KIE podling is preparing for its first Apache release. Due to the
numerous artifacts we build across various repositories (container
images, Java libraries, web apps, etc.), we seek to automate the SVN
upload as part of our release procedures.
Note: Currently, the KIE podli
