Hi Michael,
That sounds interesting, I propose to create a Jira of maybe even a wiki page
for that, maybe a new thread to discuss?
Jacques
Le 04/01/2022 à 17:58, Michael Brohl a écrit :
+1
with a few additions: I think that the project should have a planned roadmap with more or less fixed re
+1
with a few additions: I think that the project should have a planned
roadmap with more or less fixed release dates/cycles and a clear
pre-planned EOL plan.
We should also specify what EOL means for us and if there is a step
between. I think of making bugfixes/backports during main support
Hi All,
I'd like to discuss about OFBiz releases EOL (End Of Life) announcement.
For instance R17.12 is EOL with 17.12.08. I suggest to make it clear on site (if that's not already enough, eg*), to send an email to user ML and
maybe talk about it in social-media and the blog.
Maybe we could a
Thank you Jacques,
I have now published the change.
Jacopo
On Tue, Jan 4, 2022 at 11:53 AM Jacques Le Roux
wrote:
>
> I agree Jacopo,
>
> Will you handle it?
>
> I made those tiny changes after an answer Mark J. Cox made to Mark Thomas in
> a discussion I read on security-disc...@community.ap
I agree Jacopo,
Will you handle it?
I made those tiny changes after an answer Mark J. Cox made to Mark Thomas in a
discussion I read on security-disc...@community.apache.org :
MT: <>
MC: <>
There are at least 340+ TLPs*. So I guess it becomes worrying for the ASF.
I don't think we ar
Thank you Jacques for adding the statement: however I think it is time
to remove the entire section of 17.12.08 since we have enough releases
out of 18.12 already. The release 17.12.08 will always be available in
the archive.
Jacopo
On Sun, Jan 2, 2022 at 6:55 PM wrote:
>
> This is an automated
