I agree that there are good technical and sentimental reasons to
release through RubyForge but there's enough involved in putting the
release together that I'd argue it's a secondary concern since so much
of the Ruby community is based around Github now. If you run short on
time then put together the announcement and release through gh and
someone else (I volunteer) can update the rubyforge piece later if
needed.
Might also be good to send the gh guys a note letting them know that
ccrb is out with official git support.
Cheers,
Brian
On Jun 30, 2009, at 7:53 AM, Alexey Verkhovsky <[email protected]
> wrote:
Here are a few (none of them very strong, but): people watching
RubyForge for new versions is one reason I can think of. Ability to
deal with the released versions, as opposed to just random Git
snapshots is another. Not having to maintain hyperlinks to a
specific version (pointing to the entire download area instead) is
the third. Also, the sentimental value of RubyForge :) That's about
it.
On Tue, Jun 30, 2009 at 8:17 AM, C. K. Ponnappa
<[email protected]> wrote:
Folks, github allows you to download a snapshot of any revision,
including tags. I've tried it with the Rails project on github, and
the url *is* reusable, and supplies both .tar and .zip. Is there any
reason for us to continue using Rubyforge releases?
--Alex
_______________________________________________
Cruisecontrolrb-developers mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
_______________________________________________
Cruisecontrolrb-developers mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
