develooper Front page | perl.perl5.porters | Postings from October 2009

What Does it Take to Make a Maintenance Release? (was Re: sustainable development)

Thread Previous | Thread Next
From:
chromatic
Date:
October 17, 2009 13:44
Subject:
What Does it Take to Make a Maintenance Release? (was Re: sustainable development)
Message ID:
200910171344.08391.chromatic@wgz.org
On Saturday 17 October 2009 13:36:14 Nicholas Clark wrote:

> Indeed. Whilst I would love to see small, frequent maintenance releases
> after the first of a branch, I'm not going to do it, and I'm not in a
> position to cause anyone else to do it. So, I have to assume that it's not
> going to happen, whatever I would like.

Assume for a moment that we had a ready stream of capable volunteers who could 
collectively produce a maintenance release.

What kind of work would they need to do to produce a maintenance release?

Let's assume, for the sake of argument, that we have all of the resources we 
need to do so.  What type of work is it?  What resources does it require?  
What knowledge or time committment or availability or experience or hardware 
do these mythical volunteers need?

Only with that in mind am I comfortable discussing the scope of these proposed 
releases or the availability or non-availability of volunteers.

-- c

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About