Request for ruby-dbi 0.1.1 to be released

By updating the ChangeLog, I mean maintaining the list of
changes in  
this version ... I usually get them out of the CVS history,
myself.  
And then there's the job of tagging the release in CVS,
etc.

Maybe this is the sort of thing we should do together. I'll
try to  
hang out in #ruby-dbi on freenode this weekend and we can do
this  
then. Sound good?

Francis Hwang
http://fhwang.net/



On Aug 9, 2006, at 12:05 AM, Paul DuBois wrote:

> ChangeLog: Do you mean just the date on the first line,
or  
> something else?
>
> Issuing a release: Is that just a matter of clicking
the " To  
> create a new
> release click here." button on the Files page and
filling in the  
> form on the
> next page?
>
> On 8/8/06 21:06, "Francis Hwang"
<serafhwang.net> wrote:
>
>> I suppose you could just do the release yourself
... can the
>> changelog be updated, though?
>>
>> Francis Hwang
>> http://fhwang.net/
>>
>>
>>
>> On Aug 8, 2006, at 9:18 AM, Paul DuBois wrote:
>>
>>> All,
>>>
>>> I've made a number of changes to the Mysql.rb
driver since the 0.1.0
>>> release, and I don't any others planned for
the near future.  I'd
>>> like to
>>> see these become available in a public
distribution, so I request  
>>> that
>>> ruby-dbi 0.1.1 be released based on the current
sources.
>>>
>>> Or is this something that I should attempt to
do myself, assuming
>>> of course
>>> that it's okay with the primary maintainers?
>>>
>>> Thanks.
>>>
>>>
>>> _______________________________________________
>>> Ruby-dbi-next mailing list
>>> Ruby-dbi-nextrubyforge.org
>>> h
ttp://rubyforge.org/mailman/listinfo/ruby-dbi-next
>>
>> _______________________________________________
>> Ruby-dbi-next mailing list
>> Ruby-dbi-nextrubyforge.org
>> h
ttp://rubyforge.org/mailman/listinfo/ruby-dbi-next
>>
>
>

_______________________________________________
Ruby-dbi-next mailing list
Ruby-dbi-nextrubyforge.org
h
ttp://rubyforge.org/mailman/listinfo/ruby-dbi-next