Message 197421 - Python tracker

➜

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

In-reply-to
Author	orsenthil
Recipients	ncoghlan, orsenthil, r.david.murray
Date	2013年09月10日.05:15:45
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1378790146.59.0.333540854581.issue18967@psf.upfronthosting.co.za>

Content
Couple of strategies I thought for tacking this problem. 1) Documenting the resolution of NEWS specific merge conflict. Observing/recording when those arises and when it was there was no-conflict will be helpful. This could help us in organizing NEWS file in a manner that less conflicts occur. 2) Automatic generation of NEWS file from commit logs. We can tag commit logs like #NEWS-Lib-2.7, #NEWS-Core-3.4 and NEWS file can be auto generated from the log. This could be interesting, it could also be error prone. That's probably the reason why we (or any other OSS project) has not adopted this method already.

Content

Couple of strategies I thought for tacking this problem.
1) Documenting the resolution of NEWS specific merge conflict. Observing/recording when those arises and when it was there was no-conflict will be helpful. This could help us in organizing NEWS file in a manner that less conflicts occur.
2) Automatic generation of NEWS file from commit logs. We can tag commit logs like #NEWS-Lib-2.7, #NEWS-Core-3.4 and NEWS file can be auto generated from the log. This could be interesting, it could also be error prone. That's probably the reason why we (or any other OSS project) has not adopted this method already.

History
Date	User	Action	Args
2013年09月10日 05:15:46	orsenthil	set	recipients: + orsenthil, ncoghlan, r.david.murray
2013年09月10日 05:15:46	orsenthil	set	messageid: <1378790146.59.0.333540854581.issue18967@psf.upfronthosting.co.za>
2013年09月10日 05:15:46	orsenthil	link	issue18967 messages
2013年09月10日 05:15:45	orsenthil	create

homepage