Sounds good. I went ahead and put this into Jira 
https://issues.apache.org/jira/browse/OODT-65 and assigned it to me. I'll make 
sure and resolve it before 0.2 releases.

--PR

On Dec 1, 2010, at 7:04 AM, Mattmann, Chris A (388J) wrote:

> Big +1!
> 
> Let's update it. I think Paul volunteered to be the next RM, so Paul please 
> review whatever Sean adds in there about publishing to the Cheeseshop. It 
> should be a post step of the actual release VOTE (and its passing), probably 
> done at the same time we copy the release tarballs to the mirrors. I guess 
> one step we should do also is making sure we do the dist URL pointing back at 
> the Apache mirror infra like you said, there will probably be some trickery 
> required there.
> 
> BTW, I think Avro [1] does both Java and Python (PyPI releases).
> 
> Cheers,
> Chris
> 
> [1] http://avro.apache.org
> 
> On Dec 1, 2010, at 6:01 AM, Sean Kelly wrote:
> 
>> Anyone mind if we update the release process (http://s.apache.org/k6) to 
>> include publishing the metadata of the Python "Agility" OODT code to Python 
>> Package Index?
>> 
>> The Python Package Index (aka "Cheeseshop", http://pypi.python.org/) is the 
>> de jure method for automatically downloading and installing Python code, 
>> much as Maven is the de facto method for Java code.
>> 
>> We don't have to host actual distributions there, though. Those can stay 
>> within Apache's mirroring infrastructure.
>> 
>> --k
>> 
>> PS: Are there any other Java+Python projects under Apache aegis? If so, how 
>> do they do it?
>> 
> 
> 
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: [email protected]
> WWW:   http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 

Reply via email to