Patch Workflow

This is a '''very draft''' docs that aims to have a defined workflow for sending and applying patch.

{{draft|This doc aims to have a defined workflow for sending and applying patches.

 

It provides a background both for alpine developers and contributors.

It provides a background both for alpine developers and contributors.

It's in the form of FAQ, but it might be changed with a better approach.

It's in the form of FAQ, but it might be changed with a better approach.

 

Also, a graphical workflow would be useful. A nice idea is here: [https://sourceware.org/glibc/wiki/Patch%20Review%20Workflow]}}

Also, a graphical workflow would be useful. A nice idea is here: [https://sourceware.org/glibc/wiki/Patch%20Review%20Workflow]

 

== I want to contribute to Alpine project by sending patches.  How can i do this? ==  

== I want to contribute to Alpine project by sending patches.  How can i do this? ==  

First of all, thanks :)

First of all, thanks :)

Please, take a look at [[Development_using_git]] and docs linked to it.

Please, take a look at [[Development using git]] and docs linked to it.

== How should i submit a patch to alpine-aports ML?  ==  

== How should i submit a patch to alpine-aports ML?  ==  

You can follow this document: [[Creating_patches]]

You can follow this document: [[Creating patches]]

Please note that Patchwork is able to catch the patch if they are sent inline, rather than as attachment.

Please note that Patchwork is able to catch the patch if they are sent inline, rather than as attachment.

== Ok, now i've an aports git tree ready and i've sent a patch to alpine-aports ML. And now? ==

== OK, now I've an aports git tree ready and I've sent a patch to alpine-aports ML. And now? ==

Well done. Now the patch is in our workflow.

Well done. Now the patch is in our workflow.

There's a web interface where you can see all the patches sent to git.

There's a web interface where you can see all the patches sent to git.

From there,  alpine delevopers will check the patch and proceed accordingly.

From there,  alpine developers will check the patch and proceed accordingly.

Workflow status are:

Workflow status are:

Changes Requested:

Changes Requested:

     The patch looks mostly OK, but requires some rework before it will be accepted for mainline. Awaiting Upstream::  

     The patch looks mostly OK, but requires some rework before it will be accepted for mainline. Awaiting Upstream::  

Superseeded:

Superseded:

     Patches are marked as 'superseeded' when the poster submits a new version of these patches.  

     Patches are marked as 'superseded' when the poster submits a new version of these patches.  

Deferred:

Deferred:

     Deferred usually means the patch depends on something else that isn't upstream, such as patches that only apply against some specific other repository.  

     Deferred usually means the patch depends on something else that isn't upstream, such as patches that only apply against some specific other repository.  

This is the right way to change state.

This is the right way to change state.

Generally speaking, change the state on webif is not needed.

Generally speaking, change the state on webif is not needed.

Webpage only report what the user does with pwclient tool.

Web page only report what the user does with pwclient tool.

    

    

.2 On your local build environment, you need pwclient:

.2 On your local build environment, you need pwclient:

     apk add pwclient  

     apk add {{pkg|pwclient}}

     cd $your_aports_dir

     cd $your_aports_dir

     pwclient list

     pwclient list