Yikes.  Ok, noted.  We've had better success before of getting data
and participation from "prediction markets" than just sending out
opinion emails before or discussion lists.  Since it's free, and I
love Rails, and I'm not selling viagra thought I could contribute
something fun for the core group to play with.




On Aug 7, 9:05 am, Pratik <[EMAIL PROTECTED]> wrote:
> I agree with Josh. Additionally, why would you repeat the same
> question if it was already discussed in the past.
>
> On 8/7/07, inkling <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > Sorry if we a difference of opinion, but I think its very relevant
> > information to get from the core group if there is some kind of
> > consensus from them on a Rails 2.0 release.  I know a bit where Koz
> > thinks this is going to land, but not others.
>
> > Also from example, this is has been a type of question posed to this
> > list before:
>
> >http://groups.google.com/group/rubyonrails-core/browse_thread/thread/...
>
> > On Aug 7, 8:46 am, Josh Susser <[EMAIL PROTECTED]> wrote:
> > > > I know there have been discussions here about a date for this, and I
> > > > know 1.2.4 is coming before Rails 2.0 is.  And I know everyone is
> > > > working their butts off, so this isn't trying to antagonize at all,
> > > > just thought it might be fun to see what the market says when Rails
> > > > 2.0 is coming.
>
> > > This is the sort of discussion for the rubyonrails-talk list.  Please
> > > keep this list for conversations that will actually contribute toward
> > > future releases.
>
> > > --
> > > Josh Susserhttp://blog.hasmanythrough.com
>
> --
> Cheers!
> - Pratikhttp://m.onkey.org


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Core" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-core?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to