On 10/1/07, Luis Villa <[EMAIL PROTECTED]> wrote:
> On 9/30/07, Luke Melia <[EMAIL PROTECTED]> wrote:
> > My question to the group is: should we upgrade to Rails 2.0 before the
> > Tracks 1.5 release?
> >
> > I'm inclined to do so, as some of the features will clean up some portions
> > of Tracks a bit. I also find Tracks to be a great vehicle to learn new
> > version of Rails, because it leverages so many aspects of the framework. On
> > the down side, we open ourselves to bugs, incompatible plugins and more
> > outside-of-Tracks issues that we would need to investigate and help get
> > fixed.
>
> My thinking on releases is very GTD-like: break it down into small,
> manageable tasks, and get each of those done quickly, instead of
> making the release bigger and less well-defined. You'll feel better
> when you've gotten several small releases done, and it'll make the
> overall work go by faster. As a bonus users will be happier ;)
>
> So, concretely, I'd recommend looking at whatever prevents a release
> tomorrow, pulling together those loose ends, getting *something* out
> (it has been what, at least a year?), and then porting to 2.0 and/or
> whatever big feature comes next. You'll feel much more like something
> has actually been accomplished, and it'll help you resist the urge to
> spend the next year porting/polishing/refactoring/etc.
>
> Release early, release often-
> Luis
>
> P.S. I didn't realize you were in NY, Luke; I owe you a beer sometime.
>
> Luis

I agree, there is a group of us that have not upgraded since the last
release (18+ months ago).  I think stabilizing that huge amount of
work into a release prior to restructuring for Rails 2.0 would make a
lot of since.

Greg
-- 
Greg Freemyer
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer

The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com
_______________________________________________
Tracks-discuss mailing list
[email protected]
http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss

Reply via email to