cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: [VOTE] preservation policy for third-party snapshot sources
Date Tue, 29 Jun 2004 06:26:37 GMT
I'm not against including the sources somewhere in our CVS, I'm just
against including the source in the (binary) jar.

But I would prefer to not include the sources in our CVS as you
can always grep them from the CVS of the third party project.

Carsten 

> -----Original Message-----
> From: Ralph Goers [mailto:Ralph.Goers@dslextreme.com] 
> Sent: Tuesday, June 29, 2004 3:32 AM
> To: dev@cocoon.apache.org
> Subject: RE: [VOTE] preservation policy for third-party 
> snapshot sources
> 
> Interesting argument. However, if I was deploying something 
> with a snapshot into production I sure as heck would want to 
> make sure I had the source code for the snapshot to debug any 
> problems that might arise.  I've complained about this before.
> 
> Sylvain made it pretty clear that snapshots wouldn't be used 
> in formal Cocoon releases, so this procedure would never 
> apply to those. In the past this hasn't been followed. If 
> that happens in the future I would want the snapshot source 
> with the release.  For stuff still in dev I'm not sure it 
> matters whether the source goes out or not since it is pretty 
> risky to deploy such a thing in production.
> 
> My 2 cents anyway.
> 
> Ralph
> 
> At 6/28/2004  07:11 AM, you wrote:
> 
> > > Can you elaborate? Is there a technical reason except size?
> > >
> >My main concern is size. I don't see any reason for deploying source 
> >code in production environments.
> >
> >Carsten
> 
> 


Mime
View raw message