Re: [hylafax-users] new community site

["Darren Nickerson" <darren.nickerson@xxxxxxxx>]

"Lee Howard" <faxguy@xxxxxxxxxxxxxxxx> wrote:

> I've also started uploading "sub-releases" to the Sourceforge HylaFAX 
> site.  My thoughts behind sub-releases are to simply label a cut of CVS 
> HEAD at regular, frequent (like every month during periods of "heavy" 
> development) as a sub-release and hang it up on there.  The intent of this 
> is to increase exposure to new developments and fixes in the code without 
> needing to battle through the sometimes lengthy release process.

Lee,

As you know, nightly CVS snapshots have been available at ftp.hylafax.org 
for years. They're at:

   ftp://ftp.hylafax.org/source/hylafax-SNAPSHOT.tar.gz

The most recent one is dated 2 November and was cut at 1:30AM PST. Anyone 
who wants to follow the bleeding edge of HylaFAX development can either 
check out CVS themselves, or use this snapshot.

If you are going to change the HylaFAX release process, I think you should 
do it in a democratic way and involve the hylafax-devel community in an open 
discussion and a vote. That's the way myself and many other long-standing 
contributors have always worked, the entire reason for hylafax.org was to 
break out of the Ivory Tower development model into a democratic one (as 
close as possible to the Bazaar). I know you haven't always agreed with the 
concensus decisions, but they are exactly that - concensus decisions that 
have been reached after open, public discussions.

I'm curious - when do you decide it's time to cut a new release of the Lee 
Howard HylaFAX? On the -devel mailing list there's a well-established, 
time-tested orderly process of feature freeze, then code freeze, then 
bugfixing followed by betas, release candidates and finally release. Each of 
these steps are done democratically, with parties being free to influence 
the process as much as they like. What will your release policy be, and will 
you be the ultimate decider of when a new sub-release is cut or will you 
involve others in the decision?

As I said before, I can only hope you have been responsible about this, and 
that you have consulted most of the active developers and secured their 
support for this change. Otherwise, it seems irresponsible and will only 
serve to confuse and fragment the community.

-Darren 


____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*