cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vadim Gritsenko <vadim.gritse...@verizon.net>
Subject Re: [Proposal] All POI committers given access to POI block Re: [GUMP] Build Failure - cocoon-block-poi
Date Tue, 13 May 2003 12:35:58 GMT
Andrew C. Oliver wrote:

>Hi,
>
>How would you guys feel about giving all POI committers CVS access to the
>HSSF Serializer block?
>
>The only downside may be granularity of CVS control, but that could be
>gotten around by saying "don't commit outside of the block" to the
>committers who are all reasonable nice guys.
>
>The advantage:  While I hope around the world, they will have the ability to
>fix these kinds of things.
>
>Alternatively, I'm game to see it moved to the POI module and genericized to
>be non-cocoon specific.
>
>Thoughts? (both lists)
>  
>

Here is an issue: some time ago we decided to use in Cocoon CVS only 
released versions of the libraries. Meaning, once you change POI APIs in 
backward incompatible way, you first need to make a release and then it 
can be put into Cocoon. (How) Will this work for you?

Vadim


>-Andy
>
>
>On 5/11/03 4:53 AM, "Gump@icarus.apache.org" <Gump@icarus.apache.org> wrote:
>
>  
>
>>----------------------------------------------------
>>This email is autogenerated from the output from:
>><http://cvs.apache.org/builds/gump/2003-05-11/cocoon-block-poi.html>
>>----------------------------------------------------
>>    
>>
...



Mime
View raw message