Re: [Rails-devel] GUI testing (was Re: Bug fix: 1856 dit upgrade phases)

[Stefan F. <ste...@we...>]

Frederick:
the current release cycle makes the x.x.0 a kind of beta release already 
as this is the moment where program changes get exposed
to the users.

I do not like tagging (open source) releases as beta, as either they are 
releases or not. Open source/GPL software is run on your own risk anyway.

But I have an idea that might work in that direction: Sourceforge allows 
to tag the "latest version" manually and this is the offered default 
download. For a x.x.0 release this tag would not be applied and thus 
only users actively looking for the x.x.0 release would get that.

Are there any objections to this procedure?

Stefan


On 02/09/2012 06:34 PM, Frederick Weld wrote:
> Stefan:
> As an additional thought, we could change the release procedure such
> that major/minor releases (eg. 1.7.0) are tagged as beta at first. By
> doing so, we could close the gap between our current alpha testing and
> the release consumption by the end-users. I think we would have enough
> users that would be willing to use a beta release / report bugs but
> who fall short of setting up / maintaining a local git clone.
>
> What's your take on this?
>
> -- Frederick
>
> ------------------------------------------------------------------------------
> Virtualization&  Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel