Re: Migration from ci.a.o

2022-01-14 Thread Jacques Le Roux

Le 11/01/2022 à 17:54, Jacques Le Roux a écrit :

Le 15/12/2021 à 17:22, Jacques Le Roux a écrit :

Le 14/12/2021 à 09:34, Jacques Le Roux a écrit :

I also wonder if we should not get rid of Apache XMLRPC knowing that it's no 
longer maintained: https://github.com/advisories/GHSA-6vwp-35w3-xph8


A milder mitigation would be to simply comment out the 2 tests that fail on BuildBot. That would allow to keep XMLRPC for those interested. Like 
people working in a safe (ie no internet) environment. We also know that only post-auth attacks are possible.


Opinions?

Jacques


Hi,

Sorry I forgot to send this email I created one month ago

This is done, for now only trunk and R18 works: https://ci2.apache.org/#/builders (look 
for "ofb")

I'm currently working to integrate also R20.


Hi,

Of course I meant R22. It's now operational, though the currently assigned BuildBot worker (bb_worker4_ubuntu) is stale. Nevertheless, I was able to 
test using the bb_worker5_ubuntu worker. We need to wait for the "more technical" (last) point below to be able to use a kind of carousel to 
automatically pick one available worker among others


Jacques


We are still waiting for Infra for several missing features, the most important 
being missing status emails: INFRA-22689
Also are missing, faculty to start a build from IRC and, more technical, the 
possibility to use several servers to launch builds.
We had all that before...

Jacques



Re: Remove Jira archived versions?

2022-01-14 Thread Jacques Le Roux

Hi,

If nobody is against I'll made some cleaning Monday

Jacques

Le 11/01/2022 à 08:10, Jacques Le Roux a écrit :

Hi,

Should we don't remove Jira archived versions and, as explained here*, "remove 
references to the version[s] to be deleted."

Take this as an example: https://s.apache.org/qttp7 (OFBIZ-12479 is apart)

* 
https://confluence.atlassian.com/adminjiraserver/managing-versions-938847201.html#Managingversions-Deleteaversion

PS: maybe only versions referenced, or?

Jacques



Re: Add CHANGELOG.md file

2022-01-14 Thread Jacques Le Roux

Hi,

If nobody is against I'll remove this file Monday. Note that it will still be 
available in Git history/log...

Jacques

Le 09/01/2022 à 09:17, Jacques Le Roux a écrit :

But if we don't do anything about it, why keep this misleading file until we 
really start?

Le 21/12/2021 à 12:33, Jacques Le Roux a écrit :

Exactly...

Le 21/12/2021 à 12:30, Michael Brohl a écrit :

I think we'll need a process to fill it, the file alone will obviously not be 
sufficient.

Michael


Am 21.12.21 um 11:46 schrieb Jacques Le Roux:

Hi All,

OK we have a CHANGELOG file now for 10 months, but nothing in it, so?

Jacques

Le 19/06/2020 à 12:19, Deepak Dixit a écrit :

Here is the link for task
https://issues.apache.org/jira/browse/OFBIZ-11839

Thanks & Regards
--
Deepak Dixit
ofbiz.apache.org


On Thu, Jun 18, 2020 at 10:22 AM Swapnil M Mane
wrote:


+1

- Best regards,
Swapnil M Mane,
ofbiz.apache.org



On Wed, Jun 17, 2020 at 11:23 AM Deepak Dixit  wrote:


Hi Dev,

As we have already moved to git for the version control system, I propose
to add a changelog file to maintain the changelogs[1].
What is a changelog?

A changelog is a file which contains a curated, chronologically ordered
list of notable changes for each version of a project.
Why keep a changelog?

To make it easier for users and contributors to see precisely what

notable

changes have been made between each release (or version) of the project.
Who needs a changelog?

People do. Whether consumers or developers, the end users of software are
human beings who care about what's in the software. When the software
changes, people want to know why and how.

We can have our own process to generate changelog, It may be either

manual

entries, or some tool or using git log. We can discuss this

independently.

https://keepachangelog.com/en/1.0.0/

Thanks & Regards
--
Deepak Dixit
ofbiz.apache.org