oodt-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mattmann, Chris A (388J)" <chris.a.mattm...@jpl.nasa.gov>
Subject Re: [jira] Commented: (OODT-6) Import OODT Agility?
Date Mon, 22 Mar 2010 03:17:58 GMT
Hey Sean,

I think the issue is that we can¹t officially release anything in Apache
unless it¹s signed off by at least three members of the Incubator Project
Management Committee (IPMC). Also, we should probably decide how Agility
fits into the release of the rest of the OODT components. Typically the
first Incubator release is called ³0.1-incubating², per:

http://incubator.apache.org/guides/releasemanagement.html#naming

Information on how to make Incubator releases is here:

http://incubator.apache.org/guides/releasemanagement.html#intro

It¹s also good practice for us to gauge the community IMO, with an email
suggesting we¹re planning a release and then someone volunteering (or being
nominated) to be a release manager.

Interestingly enough, Apache releases need to live on Apache mirrors I
believe, so I think even if package metadata is published to PyPI, then the
source distros would still need to live at Apache. Also interesting is how
Agility should mesh with the rest of the OODT components < for OODT-15, we
were planning on making all OODT sub components live under a common
incubator/oodt/trunk. The idea I had in my mind would then be to have an
apache-oodt-0.1-incubating.tar.gz release containing all of the source code
e.g., 

incubator/oodt/tags/0.1-incubating
    /filemgr
    /workflow
    /profile
    /product
    /agility
 ...

I think we could then do things as part of the release process like:

* publish Maven artifacts of the filemgr, workflow, profile, product, etc.
to the Maven central repos
* publish Python artifacts to PyPi, e.g., for Agility

We should probably document or propose a release process, and maybe upload
it to the wiki, at:

http://cwiki.apache.org/confluence/display/OODT

Let me know what you guys think. Of course, comments from mentors here, or
advice, are also appreciated...

Cheers,
Chris

On 3/21/10 5:34 PM, "Sean Kelly" <kelly@apache.org> wrote:

> In general, the same meaning as
> http://en.wikipedia.org/wiki/Software_release_life_cycle#Software_release
> 
> Or if that URL is too long, http://is.gd/aSaA7
> 
> I can probably assume that since you're asking, I must've done something
> wrong<right?
> 
> --k
> 
> 
> On 2010.Mar.21, at 7.20p, Justin Erenkrantz wrote:
> 
>> On Sun, Mar 21, 2010 at 3:19 PM, Sean Kelly (JIRA) <jira@apache.org> wrote:
>>> 1.0.0 release
>>>   http://pypi.python.org/packages/source/o/oodt/oodt-1.0.0.tar.gz
>> 
>> What does "release" mean in this context?  -- justin
> 
> 


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: Chris.Mattmann@jpl.nasa.gov
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++



Mime
View raw message