Re: [myhdl-list] MEP guidelines

[Günter D. <dan...@we...>]

On 06.05.2011 23:07, Christopher Felton wrote:
> Sounds good.  But what is the process for ammending a MEP?  In the 
> example you provided, how would the MEP documentation be kept upto date 
> with the implementation?  Assuming the implementation diversion had 
> reasons to change the MEP.
> 
> Would a new MEP be created for the changes?

Looking at the PEP flow again, that is what they do. They create a new
PEP, that runs through the stages 'Draft' and 'Final', with the remark
that it is created to replace another PEP. If the PEP achieves the
'Final' state, the originating PEP will get its status changed from
'Final' to 'Replaced'

In think this process could be used for the MEPs as well. Then adding a
cross reference. So the old MEP gets the MEP number added by which it
got replaced and the new MEP gets the number added which it replaces.

That way the history of MyHDL implementation is documented by the MEP
documents that achieved the status 'Final' or in the process got
'Replaced'. Where as the wiki-history of the individual document shows
the development process of the MEPs.

Cheers, Guenter