You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Kevin A. Burton" <bu...@newsmonster.org> on 2005/02/22 03:05:44 UTC

[feedparser] Release HOWTO?

I'm pending on doing a first beta release of FeedParser here shortly.

Is there a document anywhere describing current release procedures 
including:

- Release Candidate scheduling
- Nighly build setup
- Gump integration
- Archive setup

... For the life of me I couldn't find anything like this.

Thanks!

Kevin

-- 

Use Rojo (RSS/Atom aggregator).  Visit http://rojo.com. Ask me for an 
invite!  Also see irc.freenode.net #rojo if you want to chat.

Rojo is Hiring! - http://www.rojonetworks.com/JobsAtRojo.html

If you're interested in RSS, Weblogs, Social Networking, etc... then you 
should work for Rojo!  If you recommend someone and we hire them you'll 
get a free iPod!
    
Kevin A. Burton, Location - San Francisco, CA
       AIM/YIM - sfburtonator,  Web - http://peerfear.org/
GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Re: [feedparser] Release HOWTO?

Posted by "Kevin A. Burton" <bu...@newsmonster.org>.
Phil Steitz wrote:

>
> Kevin A. Burton wrote:
>
>> I'm pending on doing a first beta release of FeedParser here shortly.
>>
>> Is there a document anywhere describing current release procedures 
>
>
> This is a little out of date, but a good place to start:
> http://jakarta.apache.org/commons/releases/index.html

Good god.  Those are a LOT of steps.  Has anyone automated this process 
at all?  There's no way I'm going to be doing this for every release ;)

Kevin

-- 

Use Rojo (RSS/Atom aggregator).  Visit http://rojo.com. Ask me for an 
invite!  Also see irc.freenode.net #rojo if you want to chat.

Rojo is Hiring! - http://www.rojonetworks.com/JobsAtRojo.html

If you're interested in RSS, Weblogs, Social Networking, etc... then you 
should work for Rojo!  If you recommend someone and we hire them you'll 
get a free iPod!
    
Kevin A. Burton, Location - San Francisco, CA
       AIM/YIM - sfburtonator,  Web - http://peerfear.org/
GPG fingerprint: 5FB2 F3E2 760E 70A8 6174 D393 E84D 8D04 99F1 4412


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Re: [feedparser] Release HOWTO?

Posted by Phil Steitz <ph...@steitz.com>.
Kevin A. Burton wrote:
> I'm pending on doing a first beta release of FeedParser here shortly.
> 
> Is there a document anywhere describing current release procedures 

This is a little out of date, but a good place to start:
http://jakarta.apache.org/commons/releases/index.html

> including:
> 
> - Release Candidate scheduling

Different commons components have done different things here. The most 
common approach is to follow the RC -> VOTE -> Release path described in
http://jakarta.apache.org/commons/releases/prepare.html, but the only 
thing absolutely required is that nothing is publicly released without a 
VOTE and notification of the Jakarta PMC.

> - Nighly build setup

If you have a working ant build.xml, all you need to do is post a 
request here (commons-dev list) to get added to the nightly build runs.

> - Gump integration

Not part of the release process per se and not a required prerequisite 
for a release.  I don't know of any commons gump how-to. IIRC all apache 
committers have karma for the gump repo and you can get added by just 
adding a descriptor.

> - Archive setup

Don't know exactly what you mean here.  If you mean what needs to go in 
the source and binary release tars, the minimum requirements are 
described in http://jakarta.apache.org/commons/releases/index.html

hth,

Phil

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org