[TYPO3-core] New documentation workflow

[Steffen Gebert]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> "Depends: "
What about "Documentation:" to make it more clear?

Kind regards
Steffen

- -- 
Steffen Gebert
TYPO3 v4 Core Team Member
TYPO3 Server Administration Team Member

TYPO3 .... inspiring people to share!
Get involved: http://typo3.org

I work for TYPO3 solely in my spare time. If you think that
my work helps you running your business, you are invited to
send me a donation via PayPal to this email address. Thanks

On 18.06.12 11:34, Xavier Perseguers wrote:
> Hi François,
> 
>> My proposal is the following:
>>
>> 1) Core issue is opened for a new feature
>> 2) Core patch with new feature is pushed to Gerrit
>> 3) Documentation issue is opened at the same time, with a reference to
>> the Core issue
>> 4) Core patch is merged
>> 5) Documentation patch is pushed to Gerrit
>> 6) Documentation Team reviews and merges documentation patch
> 
> I would prefer sending both patches one after the other to Gerrit
> instead of waiting for the merge to push the documentation patch to Gerrit.
> 
> In addition, having a
> 
> "Relates: "
> 
> line in the documentation patch would be good IMHO. And I would even go
> one small step further and add a
> 
> "Depends: "
> 
> line with the Change-Id of the Core patch. This allows a quick an easy
> navigation in Gerrit (I did it for a Version/Workspaces patch recently)
> and adds the dependency without making it explicitly git-wise, which
> could not be possible because we are in two separate repositories anyway.
> 
> So, to summerize:
> 
> ----- Core patch -----
> [TYPE] <Title>
> 
> <Description>
> 
> Change-Id: I<whatever>
> Resolves: #<whatever>
> Branches: 6.0, ...
> ---------------------
> 
> ----- Doc patch -----
> [DOC] <Title>
> 
> <Description>
> 
> Change-Id: I<whatever>
> Depends: <Change-Id-reference-of-the-core-patch>
> Resolves: #<whatever>
> ---------------------
> 
> I omitted the "Relates" line above, perhaps it's not really needed as we
> have the relation within Forge and if only one line should be kept I'd
> prefer the Depends one :)
> 
> Cheers
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJP366MAAoJEIskG/rSlyw47LoH/1qTibaS6y4JSvyZ7rT8vSZQ
uR5FXvJkzxDGz24y6ebRX2SUe7opokKXbePOzxFKsukCROy4M0ZAKTyZ3IVotnSA
vZLGUw1B7odpoXOoHui4rxK9OLBjtQL1zIHBHX2/6AK6gM+ID2LQCfslHS19r4rH
b0OQpVdtGPZzPCvfdbnpwOWMZpr2XMEQr0igTOEC50NJtBJitPSZS9C/Rp47HIXv
j0U9tJaVLpOEPKIg96TY//UsB8mkKeU4Vvm0nDjCghFU+kJpxKcpmRX8KojgsC/S
V3gKkc/7KSCqNX/63uPJiBOU5NmMxN54owY6NiRh2EiJjLChYh95vJbwH+t8sxw=
=3/4A
-----END PGP SIGNATURE-----