Re: enhance release experience

On 19. nov. 2014, at 13.13, Fred van Dijk <f.van.dijk-1kr/[email protected]> wrote:
> 
> I'm +1 for setting a policy to have README, CHANGES & LICENCE in root.
>> I was against this in the past but I most people I talked to believe this is a
>> good approach so let's do it.
>> 
>> However, I still believe that we should include all these three files into Sphinx
>> docs. It just makes so much sense! README has compact description about 
>> the package. What better way to start (developer) documentation in Sphinx than
>> with a compact description of what this package is all about. Also, it's helpful
>> to be able to see the CHANGES immediately in the "Contribute" section of
>> Sphinx docs.
> 
> 
> If it's included in the sphinx docs, will the merge then also be picked up to the front page
> of the package info at pypi.python.org? It's rather annoying that some packages
> (like Products.TinyMCE) don't have the changes available anymore, so with
> a new release you have to browse through readthedocs for a changelog (which isn't
> updated for P.TinyMCE either) and you end up chasing the CHANGES in the
> github repo's and/or checking commits. 

Sure, that's perfectly doable. 


z.
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk