the state of activescaffold
Lance Ivy
Kudos to Sergio for his patching and Mike for making headway on issue tracking, and for everyone else who has contributed in the last month. ActiveScaffold is back on its feet thanks to all of you!
I've decided that without an official team and a roadmap it doesn't make sense to really have versions of ActiveScaffold. What's more useful is to track ActiveScaffold against versions of Rails. So my plan is to start following Rails' version numbers. Here's how:
current branches in git:
* active_scaffold/master -- will track Rails edge. Active development should happen here, and should be against the latest versions of Rails.
* active_scaffold/rails-2.1 -- will "tag" the last known commit to work with Rails 2.1. If you need a commit from master and can verify that it works with Rails 2.1, then please fork, apply the patch, and send a pull request for this branch.
So, when Rails 2.2 final comes out, what happens? Nothing. We'll keep applying patches to master. But if they break the view template finders again (sigh), then I'll create a active_scaffold/rails-2.2 branch *before* pulling in patches to fix for edge (the future Rails 2.3 or 3.0 or whatever).
Make sense?
Summary: active development should be against the latest version of Rails, if possible, and fixes should be backported to earlier branches if needed.
-Lance
p.s. Github lets you download a zip file of any branch, which means that even if you haven't learned git, you can still download A.S. for Rails 2.1.
--
rails blog: http://codelevy.com
David Richardson
> So, when Rails 2.2 final comes out, what happens? Nothing. We'll keep
> applying patches to master. But if they break the view template finders
> again (sigh), then I'll create a active_scaffold/rails-2.2 branch *before*
> pulling in patches to fix for edge (the future Rails 2.3 or 3.0 or
> whatever).
>
> Make sense?
>
> Summary: active development should be against the latest version of Rails,
> if possible, and fixes should be backported to earlier branches if needed.
Sergio Cambra .:: entreCables - Symbol Servicios Informáticos S.L. ::.
> Hello everyone,
>
> Kudos to Sergio for his patching and Mike for making headway on issue
> tracking, and for everyone else who has contributed in the last month.
> ActiveScaffold is back on its feet thanks to all of you!
>
> I've decided that without an official team and a roadmap it doesn't make
> sense to really have versions of ActiveScaffold. What's more useful is to
> track ActiveScaffold against versions of Rails. So my plan is to start
> following Rails' version numbers. Here's how:
>
> current branches in git:
> * active_scaffold/master -- will track Rails edge. Active development
> should happen here, and should be against the latest versions of Rails.
> * active_scaffold/rails-2.1 -- will "tag" the last known commit to work
> with Rails 2.1. If you need a commit from master and can verify that it
> works with Rails 2.1, then please fork, apply the patch, and send a pull
> request for this branch.
I'm going to continue fixing bugs and improving ActiveScaffold. I use rails
2.1 currently, so I will try my patches with edge and 2.1 too.
>
> So, when Rails 2.2 final comes out, what happens? Nothing. We'll keep
> applying patches to master. But if they break the view template finders
> again (sigh), then I'll create a active_scaffold/rails-2.2 branch *before*
> pulling in patches to fix for edge (the future Rails 2.3 or 3.0 or
> whatever).
>
> Make sense?
>
> Summary: active development should be against the latest version of Rails,
> if possible, and fixes should be backported to earlier branches if needed.
I agree, but ATM rails-2.1 branch has missing commits which works with 2.1
--
Sergio Cambra .:: entreCables - Symbol Servicios Informáticos S.L. ::.
Nicolás Guillén 6, locales 2 y 3. 50.018 Zaragoza
T) 902 021 404 F) 976 52 98 07 E) ser...@entrecables.com