-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Chris / Markus,

Work has been very busy (end of year and first quarter are crazy for me)... but 
is there any specific tasks that you may need
someone to look into later this week/weekend?

Zach

Christopher Williams wrote:
> Kyle, All,
> 
> 
> On Apr 4, 2006, at 2:38 PM, Kyle Shank wrote:
> 
>> Hey all,
>>
>> We are trying to get another release of RadRails before the Canada on
>> Rails conference.  We are trying to finish off our support for the new
>> features of Rails 1.1 and will need another build of RDT.
> 
> 
> I think we should do what we can to support them and try and get a 
> release out the door.
> 
> 
>> Matt and I
>> are on to fix some issues slated for next release but to be realistic
>> I'm proposing a 0.7.1 build or something of the sort, not a complete
>> 0.8 release.
> 
> 
> I think an 0.8.0 release (at least a release candidate) is do-able.  We
> already have a lot of functionality since the 0.7.0 release, and  it's
> been working fine for me (I patched bugs with the new browsing  stuff
> locally, but until just now SF.net's CVS was down so I just  checked
> them in).
> 
> The only bug I'd like to see fixed for an 0.8.0 is the Fixnum syntax 
> highlighting - we highlight numbers inside identifiers (like method 
> names) when we shouldn't. Beyond that I'd encourage everyone to try  out
> a copy of the nightly build and make sure what's in there is  stable -
> particularly Ruby browsing, handling of RJS/RXML, the new  class wizard,
> template insertion via content assist, code formatting  and the goto
> matching bracket action.
> 
> There's release related tasks I'd like to see happen as well, but  they
> should be able to be done post-release - particularly, I'd like  to use
> RadRails experience to help us create some single-download  releases of
> 0.8.0 - so you pick the download for your platform and  get the bare
> minimum stuff you need to run RDT (plus maybe some  branding like splash
> loader screen, icon, etc).
> 
>> We plan on adding support for RJS and RXML which are just additions to
>> extension types on ruby editor and the RemoteTestRunner script.  Those
>> are the most critical changes that need to be made.
> 
> 
> RJS/RXML support are already in the latest nightly and current CVS  head
> (at least for building/parsing/editing - not sure what you mean  for
> RemoteTestRunner).
> 
> 
>> So, can this happen by the end of the weekend?  The conference is next
>> weds-fri and we need to get our full support for Rails 1.1 out the
>> door.
> 
> 
> This is up to our unofficial build master Markus. Do you have any  time
> to get a release out by the weekend?
> 
> Thanks,
> Chris
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Rubyeclipse-development mailing list
> Rubyeclipse-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFEMyJ1Myx0fW1d8G0RAkwoAJ0SboiCYt2FNeMZGtoc1KHWRrUzlACeML4q
MY3tCqDbklQvuSz+gOYRr/A=
=z0x7
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Rubyeclipse-development mailing list
Rubyeclipse-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rubyeclipse-development

Reply via email to