Re: enhance release experience

Wichert Akkerman wrote:

...
> MANIFEST.in is still very useful and important, and I disagree very
> strongly with Jens that you should not use it. I’ve come around to the
> opinion that using tools like setuptools-git should be avoided since they
> are too fragile, and will often result in completely broken packages if
> someone else tries to make a distribution.


+100.

I've never encountered a scenario where a proper MANIFEST.in was responsible 
for a brown bag release.

Without a MANIFEST.in the release-process implicitly depends on the version 
control  system + the indivual developer setup. There are hundreds of 
releases that are *accidentally* correct.
If a package does not contain a MANIFEST.in, you better assume the package-
authors are unaware of that. 

I'm responsible for adding a MANIFEST.in to plenty of packages 
(which was identical for all packages).
This made the resulting community-releases a lot more consistent then 
before. But this also avoided brown bag-releases of privately forked 
packages that are maintained in a different VCS (svn, bzr, hg), which was 
the main motivation for adding it.

The plone-community should not assume that all plone-projects are using git.







------------------------------------------------------------------------------
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
_______________________________________________
Plone-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/plone-developers