Beta-release management

2 views

Skip to first unread message

Evert Pot

unread,

Jan 26, 2010, 10:20:17 PM1/26/10

to pear...@googlegroups.com

Hi guys,

I have a simple question, but it might have a complicated answer.

I have version 1.0.5 of my package, which is 'stable'.
I'm currently working on 1.1.0, which is of 'alpha' quality.

Later down the road this will become 1.2.0, and stable again (I'm reserving even numbers for stable releases).

How would Pearfarm deal with a situation like that? Does the pear installer even allow this?

Evert

Alan Pinstein

unread,

Jan 26, 2010, 10:52:45 PM1/26/10

to pear...@googlegroups.com

You can set the stability for each release. PEAR has built-in logic to
deal with this. If you run "pear config-show" you can see the
preferred release state is set in the client, and that controls how
"instable" of a release it will try to fetch.

Pearfarm does nothing on top of PEAR's built-in logic for this.

My expectation is that if you have a 1.1.0-stable and a 1.2.0-alpha, a
"stable-only" client will not upgrade unless you do a "pear upgrade
project-alpha".