Okay, boys and girls: Let''s get ready for the release! First of all, in case you missed it: I now have full access to the RubyForge project and why''s repo at GitHub. I guess this makes me some sort of a project leader, but don''t worry: The community will still maintain Camping. I will continue pushing to my own repo and will ask the mailing list before merging any big changes. Everything will still be maintained through this mailing list. I''m not going to work on any new features (not many, but I still have some ideas left); just preparing for this release. This means (in no specific order): * Update the documentation * Update the GitHub wiki * Update the changelog * Clean up the examples * Choose a bug tracker * Write an announcement * Fix any bugs discovered while we''re cleaning up I''m working on the documentation at the moment. I''m also going to take some of the essential stuff that was on the old wiki and put it right into the RDoc. The RDoc tempate (flipbook) is currently on hold until Eric Hodel finishes his awesome refactoring of RDoc. Then I''ll convert it to the new template system and probably add search. When it comes to bug tracking, I really like ditz (http://ditz.rubyforge.org) + sheila (written in Camping; example: http://masanjin.net:9000/). What do you think? 2.0 will then be release, 2.0.x for minor fixes, 2.0.x.REV for bleeding edge (from my gem server) and 2.1 for completely new featues. Any comments or thoughts? Anyone else who want to do some of these things? Remember, I''m not _why ;-) //Magnus Holm -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/camping-list/attachments/20090214/94fa5eb3/attachment.html>
Magnus,
First, you are right, you are not _why but you are doing an
amazing job. You can throw away the little wheels.
I would be happy to contribute updating the Wiki at GitHub,
starting next saturday. Not sure what timeframe are you thinking for
the release...
Best regards,
--------------------------------
An?bal Rojas
http://hasmanydevelopers.com
http://rubycorner.com
http://anibal.rojas.com.ve
On Sun, Feb 15, 2009 at 10:13 AM, Magnus Holm <judofyr at gmail.com>
wrote:> Okay, boys and girls: Let''s get ready for the release!
>
> First of all, in case you missed it: I now have full access to the
RubyForge
> project and why''s repo at GitHub. I guess this makes me some sort
of a
> project leader, but don''t worry: The community will still maintain
Camping.
> I will continue pushing to my own repo and will ask the mailing list before
> merging any big changes. Everything will still be maintained through this
> mailing list.
> I''m not going to work on any new features (not many, but I still
have some
> ideas left); just preparing for this release. This means (in no specific
> order):
> * Update the documentation
> * Update the GitHub wiki
> * Update the changelog
> * Clean up the examples
> * Choose a bug tracker
> * Write an announcement
> * Fix any bugs discovered while we''re cleaning up
> I''m working on the documentation at the moment. I''m also
going to take some
> of the essential stuff that was on the old wiki and put it right into the
> RDoc.
> The RDoc tempate (flipbook) is currently on hold until Eric Hodel finishes
> his awesome refactoring of RDoc. Then I''ll convert it to the new
template
> system and probably add search.
> When it comes to bug tracking, I really like ditz
> (http://ditz.rubyforge.org) + sheila (written in Camping;
> example: http://masanjin.net:9000/). What do you think?
> 2.0 will then be release, 2.0.x for minor fixes, 2.0.x.REV for bleeding
edge
> (from my gem server) and 2.1 for completely new featues.
> Any comments or thoughts? Anyone else who want to do some of these things?
> Remember, I''m not _why ;-)
>
> //Magnus Holm
>
> _______________________________________________
> Camping-list mailing list
> Camping-list at rubyforge.org
> http://rubyforge.org/mailman/listinfo/camping-list
>
On Sat, 2009-02-14 at 15:43 +0100, Magnus Holm wrote:> Okay, boys and girls: Let''s get ready for the release!> > > When it comes to bug tracking, I really like ditz > (http://ditz.rubyforge.org) + sheila (written in Camping; > example: http://masanjin.net:9000/). What do you think?Sounds great! I rather like ditz. Only problem I see -- how do Ordinary Joes submit bugs? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: <http://rubyforge.org/pipermail/camping-list/attachments/20090214/f2b64fb0/attachment.bin>
On Sat, 2009-02-14 at 15:43 +0100, Magnus Holm wrote:> Okay, boys and girls: Let''s get ready for the release!> > > When it comes to bug tracking, I really like ditz > (http://ditz.rubyforge.org) + sheila (written in Camping; > example: http://masanjin.net:9000/). What do you think?Sounds great! I rather like ditz. Only problem I see -- how do Ordinary Joes submit bugs? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: <http://rubyforge.org/pipermail/camping-list/attachments/20090214/733664af/attachment.bin>
setup Sheila Ditz someplace for normal Joes? http://github.com/why/sheila/blob/master/sheila.rb -dg On Feb 14, 2009, at 9:01 AM, Aria Stewart wrote:> On Sat, 2009-02-14 at 15:43 +0100, Magnus Holm wrote: >> Okay, boys and girls: Let''s get ready for the release! > >> >> >> When it comes to bug tracking, I really like ditz >> (http://ditz.rubyforge.org) + sheila (written in Camping; >> example: http://masanjin.net:9000/). What do you think? > > Sounds great! I rather like ditz. > > Only problem I see -- how do Ordinary Joes submit bugs? > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list