Lets get the machine moving again
R. O'Connell
life interludes with making OSS projects better. I have the next few
days to work on things, so I can clear out some very pressing things.
There's a few things I see right away:
There was a suggestion to include a Gemspec in the main git repo so
people can point Bundler to it to use the latest and greatest instead
of relying on infrequent version updates.
There's some 1.92 specific bugfixes in the pull queue that should be
merged ASAP after making a Gemspec.
With these bugfixes we should release tag a new Github version and
release a new Gem so people can keep going in the meantime.
Rory
James Hewitt
Will keep an eye out and help where I can.
James.
Austin Ziegler
> I was considering doing the same prompting myself.
>
> Will keep an eye out and help where I can.
Thanks, guys. I'm a bit busy with RubyPython (which I need for a
project at work), so LDAP has fallen by the wayside (which has been
deprecated from being used in the same project at work in favour of a
different solution).
> On 16 March 2011 18:17, R. O'Connell <rory...@gmail.com> wrote:
>> We have a backlog of pull requests and, at least I know personally,
>> life interludes with making OSS projects better. I have the next few
>> days to work on things, so I can clear out some very pressing things.
>> There's a few things I see right away:
>>
>> There was a suggestion to include a Gemspec in the main git repo so
>> people can point Bundler to it to use the latest and greatest instead
>> of relying on infrequent version updates.
We're based on hoe now, so this should be as easy as "rake gemspec"
and checking in the gemspec. We might need modifications to .gitignore
to make this work.
>> There's some 1.92 specific bugfixes in the pull queue that should be
>> merged ASAP after making a Gemspec.
>>
>> With these bugfixes we should release tag a new Github version and
>> release a new Gem so people can keep going in the meantime.
-a
--
Austin Ziegler • halos...@gmail.com • aus...@halostatue.ca
http://www.halostatue.ca/ • http://twitter.com/halostatue
R. O'Connell
people can point Bundler to the repo for the bleeding edge.
Austin to you still want to continue managing releases?
On Mar 16, 2:06 pm, Austin Ziegler <halosta...@gmail.com> wrote:
> > I was considering doing the same prompting myself.
>
> > Will keep an eye out and help where I can.
>
> Thanks, guys. I'm a bit busy with RubyPython (which I need for a
> project at work), so LDAP has fallen by the wayside (which has been
> deprecated from being used in the same project at work in favour of a
> different solution).
>
> >> We have a backlog of pull requests and, at least I know personally,
> >> life interludes with making OSS projects better. I have the next few
> >> days to work on things, so I can clear out some very pressing things.
> >> There's a few things I see right away:
>
> >> There was a suggestion to include a Gemspec in the main git repo so
> >> people can point Bundler to it to use the latest and greatest instead
> >> of relying on infrequent version updates.
>
> We're based on hoe now, so this should be as easy as "rake gemspec"
> and checking in the gemspec. We might need modifications to .gitignore
> to make this work.
>
> >> There's some 1.92 specific bugfixes in the pull queue that should be
> >> merged ASAP after making a Gemspec.
>
> >> With these bugfixes we should release tag a new Github version and
> >> release a new Gem so people can keep going in the meantime.
>
> -a
> --
Austin Ziegler
> I merged larstobi's 1.92 patch and created a ruby-net-ldap.gemspec so
> people can point Bundler to the repo for the bleeding edge.
>
> Austin to you still want to continue managing releases?
I can, but most of the release functionality is built into the Rakefile now.
I will set myself a task to check who has access on RubyGems.org for a
release, but I don't have time right at the moment to do so.
Austin Ziegler
> On Wed, Mar 16, 2011 at 4:30 PM, R. O'Connell <rory...@gmail.com> wrote:
>> I merged larstobi's 1.92 patch and created a ruby-net-ldap.gemspec so
>> people can point Bundler to the repo for the bleeding edge.
>> Austin to you still want to continue managing releases?
>
> I can, but most of the release functionality is built into the Rakefile now.
>
> I will set myself a task to check who has access on RubyGems.org for a
> release, but I don't have time right at the moment to do so.
* Rory, Emiel, Kaspar, Francis, or myself SHOULD be able to push a new
gem version to RubyGems.org.
* Rory, Emiel, Kaspar, Francis, or myself SHOULD be able to scp the
rdoc to RubyForge.org.
* I've just set the RubyForge trackers to send email to the mailing list.
* I am removing the Gemfile and Gemfile.lock; those are for
applications, not libraries.
* I've added the devdeps hoe-gemspec, flexmock, and rspec.
* I've removed hanna and archive-tar-minitar (and the tar building
based on that).
* I'm fixing [#28588] Regexp waring under Ruby 1.9.2-p0 from the
tracker (mostly to test the email).
Once I get a RubyPython release out the door, I'll make a few more
changes to the Rakefile that reflect a better understanding that I've
gained with hoe Rakefiles with RubyPython, but I'll be doing those in
a branch so that it doesn't affect the current release that you're
putting together.
Austin Ziegler
* Rory, Emiel, Kaspar, Francis, or myself SHOULD be able to scp the
rdoc to RubyForge.org.