We also need doc/submitting-patches.asciidoc to be updated. I would be grateful if someone else wanted to do that...
On 1/1/23 13:36, Allan McRae wrote:
Happy new year!
I have updated the project descriptions in gitlab and flyspray to reflect where bugs should be opened and patches should be submitted.
I do not see an option to prevent new bugs being filed in flyspray. Anything opened there will be closed with a message pointing at gitlab.
I have moved some of the flyspray bugs to gitlab, and fixed a bunch that could be done quickly. Help there would be greatly appreciated.
On 5/12/22 03:41, Morten Linderud wrote:
Some time ago it was decided to migrate the pacman development from the Mailing List to the Gitlab instance hosted by Arch Linux. The pacman source has been hosted there for a while but the development has strictly been conducted on the Mailing List and this is about to change.
The plan is as follows:
- Open the patch submission via Gitlab and close the mailing list
submission 2. Open the Gitlab issue tracker and close down the flyspry issue tracker 3. Manually migrate bugs from flyspry to Gitlab and close the others.
Currently the issue tracker is open on Gitlab, and merge requests have also been enabled for some time. No EOL dates has been set on on patch submission nor flyspry, but I'd encourage any new development to using gitlab instead of the mailing list and flyspry from this point on.
I propose we close down Flyspry and patch submission 1st of January 2023.
This change also implies decommisioning the Patchwork instance. For this to be done we need to keep track of any unmerged/unreviewed patches from the mailing list. This list has been made and if anything is missing please do reach out.
There is also some documentation work that needs to be done to direct users from the Mailing List to Gitlab. Any help updating this documentation is very much appreciated.
Cheers, Morten Linderud