Re: [Rails-devel] Release strategy - master vs. rails2develop

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

Frederick:
we could do that later on. Most people now know that rails_2_develop is 
the (default) branch for rails 2.

My (future) release strategy is based on

http://nvie.com/posts/a-successful-git-branching-model/

However I still consider moving the git repo (only the repo, not the 
other parts) to github, then this will happen with the official rails 
2.0 release.

I am looking forward to seeing more maps from you.

One question: In which format and tools  do you create your maps?

Most likely you will know that I intend to replace the Batik lib soon. 
However which long-run strategy to choose how display maps/tiles for Rails.

In the short-run I will simply replace Batik by a more light-weight SVG 
library, but I am open to recommendations.

Stefan


On 12/04/2014 10:16 AM, Frederick Weld wrote:
> Stefan:
> There is no standard 1830 map yet. I will probably do that after the
> Coalfield map has been reviewed (bgg) and thoroughly play-tested.
>
> How about labeling rails_2_develop as master? Then the meaning would be
> clear: Current state of validated development which is eligible for the
> next release.
>
> -- Frederick
>
>
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> Rails-devel mailing list
> Rai...@li...
> https://lists.sourceforge.net/lists/listinfo/rails-devel
>