Today, I'd like to make some important announcements.
1) The next release of Rack will be version 0.9 and I want it to be released as soon as possible (January 2009 would be best, but I see there are some parts that still need polishing). Please send patches you want in there. This will be the last release of 0.x (apart from possible bug fix releases).
2) Rack 1.0 will follow soon after, and there will some significant changes:
* This is the chance to make possibly incompatible changes/enhancements to the code and the spec. Please propose now!
* I want full and first-class 1.9 support, thus the spec will need to be adjusted for that. (String#each, Unicode, etc.)
* I want the Rails 2.3 release to work with Rack 1.0, so we will need to coordinate releases.
* Rack has become an important part of the Ruby infrastructure and should be managed as such. Thus I have founded the Rack Core Team, which consists of:
* Christian Neukirchen (chneukirchen) * James Tucker (raggi) * Josh Peek (josh) * Michael Fellinger (manveru) * Ryan Tomayko (rtomayko) * Scytrin dai Kinthra (scytrin)
The Rack Core Team has write access to the official Rack repositories, which now reside at Github:
> Today, I'd like to make some important announcements.
> 1) The next release of Rack will be version 0.9 and I want it to be > released as soon as possible (January 2009 would be best, but I see > there are some parts that still need polishing). Please send patches > you want in there. This will be the last release of 0.x (apart from > possible bug fix releases).
> 2) Rack 1.0 will follow soon after, and there will some significant > changes:
> * This is the chance to make possibly incompatible > changes/enhancements to the code and the spec. Please propose now!
> * I want full and first-class 1.9 support, thus the spec will need to > be adjusted for that. (String#each, Unicode, etc.)
> * I want the Rails 2.3 release to work with Rack 1.0, so we will need > to coordinate releases.
> * Rack has become an important part of the Ruby infrastructure and > should be managed as such. Thus I have founded the Rack Core Team, > which consists of:
> * Christian Neukirchen (chneukirchen) > * James Tucker (raggi) > * Josh Peek (josh) > * Michael Fellinger (manveru) > * Ryan Tomayko (rtomayko) > * Scytrin dai Kinthra (scytrin)
> The Rack Core Team has write access to the official Rack > repositories, which now reside at Github:
Very cool! Can part of this initiative include some sort of ticket managing app like Lighthouse for Rack? I'd like to go to a central place to get a good idea of what people would like to see implemented or have issues with to know where to put some time in to help improve it.
Just my preference.
Matt
On Wed, Dec 24, 2008 at 2:46 PM, Ezra Zygmuntowicz <ezmob...@gmail.com>wrote:
> On Dec 24, 2008, at 3:43 AM, Christian Neukirchen wrote:
>> Today, I'd like to make some important announcements.
>> 1) The next release of Rack will be version 0.9 and I want it to be >> released as soon as possible (January 2009 would be best, but I see >> there are some parts that still need polishing). Please send patches >> you want in there. This will be the last release of 0.x (apart from >> possible bug fix releases).
>> 2) Rack 1.0 will follow soon after, and there will some significant >> changes:
>> * This is the chance to make possibly incompatible >> changes/enhancements to the code and the spec. Please propose now!
>> * I want full and first-class 1.9 support, thus the spec will need to >> be adjusted for that. (String#each, Unicode, etc.)
>> * I want the Rails 2.3 release to work with Rack 1.0, so we will need >> to coordinate releases.
>> * Rack has become an important part of the Ruby infrastructure and >> should be managed as such. Thus I have founded the Rack Core Team, >> which consists of:
>> * Christian Neukirchen (chneukirchen) >> * James Tucker (raggi) >> * Josh Peek (josh) >> * Michael Fellinger (manveru) >> * Ryan Tomayko (rtomayko) >> * Scytrin dai Kinthra (scytrin)
>> The Rack Core Team has write access to the official Rack >> repositories, which now reside at Github:
"Matt Todd" <chiol...@gmail.com> writes: > Very cool!
> Can part of this initiative include some sort of ticket managing app like > Lighthouse for Rack? I'd like to go to a central place to get a good idea of > what people would like to see implemented or have issues with to know where to > put some time in to help improve it.
> Just my preference.
> Matt
Sounds good... which one? Lighthouse, Google Code, Rubyforge?
On 25.12.2008, at 0:14, Christian Neukirchen wrote:
> Sounds good... which one? Lighthouse, Google Code, Rubyforge?
A lot of people in the Ruby community have a LH account already, and frankly, Rubyforge is awful for nearly anything (IMO). Google Code is tied to Subversion. GitHub has fair integration with LightHouse.
Michael Klishin <michael.s.klis...@gmail.com> writes: > On 25.12.2008, at 0:14, Christian Neukirchen wrote:
>> Sounds good... which one? Lighthouse, Google Code, Rubyforge?
> A lot of people in the Ruby community have a LH account already, and > frankly, Rubyforge is awful for nearly anything (IMO). > Google Code is tied to Subversion. GitHub has fair integration with > LightHouse.
> Michael Klishin <michael.s.klis...@gmail.com> writes:
> > On 25.12.2008, at 0:14, Christian Neukirchen wrote:
> >> Sounds good... which one? Lighthouse, Google Code, Rubyforge?
> > A lot of people in the Ruby community have a LH account already, and > > frankly, Rubyforge is awful for nearly anything (IMO). > > Google Code is tied to Subversion. GitHub has fair integration with > > LightHouse.
>> Can part of this initiative include some sort of ticket managing >> app like >> Lighthouse for Rack? I'd like to go to a central place to get a >> good idea of >> what people would like to see implemented or have issues with to >> know where to >> put some time in to help improve it.
>> Just my preference.
>> Matt
> Sounds good... which one? Lighthouse, Google Code, Rubyforge?
>>> Can part of this initiative include some sort of ticket managing app like >>> Lighthouse for Rack? I'd like to go to a central place to get a good idea >>> of >>> what people would like to see implemented or have issues with to know >>> where to >>> put some time in to help improve it.
>>> Just my preference.
>>> Matt
>> Sounds good... which one? Lighthouse, Google Code, Rubyforge?
Pivotal Tracker can't be used (presently) in an open enough fashion to use it on OSS. We *strongly* considered using it for Merb, but you have to manually invite each user for them to be able to view it. Perhaps if we expressed interest to them, they'd add OSS capabilities. -- Yehuda
On Wed, Dec 24, 2008 at 10:06 PM, Matt Todd <chiol...@gmail.com> wrote: > Pivotal Tracker? I've never used it for an open source project, though that > sounds like an interesting idea. > Matt
> On Wed, Dec 24, 2008 at 11:39 PM, James Tucker <jftuc...@gmail.com> wrote:
>> On 24 Dec 2008, at 17:14, Christian Neukirchen wrote:
>>>> Can part of this initiative include some sort of ticket managing app >>>> like >>>> Lighthouse for Rack? I'd like to go to a central place to get a good >>>> idea of >>>> what people would like to see implemented or have issues with to know >>>> where to >>>> put some time in to help improve it.
>>>> Just my preference.
>>>> Matt
>>> Sounds good... which one? Lighthouse, Google Code, Rubyforge?
"Yehuda Katz" <wyc...@gmail.com> writes: > Pivotal Tracker can't be used (presently) in an open enough fashion to use it > on OSS. We *strongly* considered using it for Merb, but you have to manually > invite each user for them to be able to view it. Perhaps if we expressed > interest to them, they'd add OSS capabilities.
> -- Yehuda
I'd prefer something open, with low-as-possible effort to report bugs.
>> Pivotal Tracker can't be used (presently) in an open enough fashion >> to use it >> on OSS. We *strongly* considered using it for Merb, but you have to >> manually >> invite each user for them to be able to view it. Perhaps if we >> expressed >> interest to them, they'd add OSS capabilities.
>> -- Yehuda
> I'd prefer something open, with low-as-possible effort to report bugs.
