Re: The 2.2 release
On Sat, Sep 06, 2014 at 11:08:04PM +0200, Paul van Tilburg wrote: I'd be happy with a 2.1.x release though! So, what is this numbering after 2.1 about actually? What is the system? What are your experiences with AR4 and Camping? I've made some adjustments (mainly to most queries) in my application but it seems to run fine now. What about you guys? Cheers, Paul -- Web: http://paul.luon.net/home/ | E-mail: p...@luon.net Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
The 2.2 release
Hi, While I am quite aware that development has pretty much stalled, I wondered if it would still be possible to have some kind of 2.2 release out[1]? For me, Camping still works just great with my applications and also with AR4, so I am still quite happy with it. I am currently working on the Debian packaging again, since a freeze for the upcoming release is nigh. At the moment Debian ships version 2.1.532, but it doesn't work with AR4. I've noticed that HEAD _does_ work for me, but I'd prefer not to ship 2.1.532+gitsome snapshot unless necessary. So I was wondering: is it release ready (see also [1]) and what are the experiences of you guys with the current state of Camping? Cheers, Paul 1: https://github.com/camping/camping/milestones/Camping%202.2 -- Web: http://paul.luon.net/home/ | E-mail: p...@luon.net Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: The 2.2 release
I can easily release a new 2.1.x. Not sure if we need a 2.2 yet? On Saturday, September 6, 2014, Paul van Tilburg p...@luon.net wrote: Hi, While I am quite aware that development has pretty much stalled, I wondered if it would still be possible to have some kind of 2.2 release out[1]? For me, Camping still works just great with my applications and also with AR4, so I am still quite happy with it. I am currently working on the Debian packaging again, since a freeze for the upcoming release is nigh. At the moment Debian ships version 2.1.532, but it doesn't work with AR4. I've noticed that HEAD _does_ work for me, but I'd prefer not to ship 2.1.532+gitsome snapshot unless necessary. So I was wondering: is it release ready (see also [1]) and what are the experiences of you guys with the current state of Camping? Cheers, Paul 1: https://github.com/camping/camping/milestones/Camping%202.2 -- Web: http://paul.luon.net/home/ | E-mail: p...@luon.net javascript:; Jabber/GTalk: p...@luon.net javascript:; | GnuPG key ID: 0x50064181 ___ Camping-list mailing list Camping-list@rubyforge.org javascript:; http://rubyforge.org/mailman/listinfo/camping-list -- // Magnus Holm ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: The 2.2 release
On Sat, Sep 06, 2014 at 09:41:00PM +0200, Magnus Holm wrote: I can easily release a new 2.1.x. Not sure if we need a 2.2 yet? I am not sure either, especially since the milestone has open issues but I wonder if they still should all be open. Are there other 2.2 goals? I'd be happy with a 2.1.x release though! Cheers, Paul -- Web: http://paul.luon.net/home/ | E-mail: p...@luon.net Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Camping release?
Hi Paul just checking if you got a response yet - what's the approximate deadline date? I notice that Camping 2.0 is in Squeeze: http://packages.debian.org/squeeze/camping Also, are your Camping apps public? If so, I'd like their URLs so we can include them in a 'made with Camping' list... Dave Everitt Hey all, The new Debian release is freezing soon (about 2 weeks) and I would really like it to include Camping 2.2 with Mab 0.0.2. Given that Markaby isn't actually distributable, I have recently uploaded Camping 2.1.498 with a Git snapshot of Mab to test some transitions. I have adapted (changed 'text' calls into 'text!' mainly) and tested two of my main applications and they seem to work nicely! So, the question is: what is still needed for the 2.2 release (Magnus mentioned something about a change log update but there is probably more) and how can I/we help to expedite this? Cheers, Paul (Camping maintainer in Debian) -- Web: http://paul.luon.net/home/ | E-mail: p...@luon.net Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Camping release?
Hey, On Wed, May 30, 2012 at 04:55:25PM +0100, Dave Everitt wrote: just checking if you got a response yet - what's the approximate deadline date? I think I have another week, maybe two. I notice that Camping 2.0 is in Squeeze: http://packages.debian.org/squeeze/camping It is, if not for the Camping snapshot upload, it would have to be removed, as Camping 2.0 and 2.1 depend on Markaby, while 2.2 will depend on Mab. Also, are your Camping apps public? If so, I'd like their URLs so we can include them in a 'made with Camping' list... Not yet, but soon. I will let you know, thanks. :) Paul -- Web: http://paul.luon.net/home/ | E-mail: p...@luon.net Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Camping release?
Hey all, The new Debian release is freezing soon (about 2 weeks) and I would really like it to include Camping 2.2 with Mab 0.0.2. Given that Markaby isn't actually distributable, I have recently uploaded Camping 2.1.498 with a Git snapshot of Mab to test some transitions. I have adapted (changed 'text' calls into 'text!' mainly) and tested two of my main applications and they seem to work nicely! So, the question is: what is still needed for the 2.2 release (Magnus mentioned something about a change log update but there is probably more) and how can I/we help to expedite this? Cheers, Paul (Camping maintainer in Debian) -- Web: http://paul.luon.net/home/ | E-mail: p...@luon.net Jabber/GTalk: p...@luon.net | GnuPG key ID: 0x50064181 ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Camping 2.2 pre-release
failing test case, running in camping:
def layout
text !DOCTYPE html\n
html { head { title foo } }
end
Markaby output:
!DOCTYPE html
htmlheadtitlefoo/title/head/html
Mab output:
lt;!DOCTYPE htmlgt;
htmlheadtitlefoo/title/head/html
—
Jenna Fox
On Wednesday, 25 January 2012 at 10:00 PM, Magnus Holm wrote:
gem install camping --source http://gems.judofyr.net/
___
Camping-list mailing list
Camping-list@rubyforge.org
http://rubyforge.org/mailman/listinfo/camping-list
Re: Maintenance release of 2.1
On Sun, Oct 2, 2011 at 14:26, Jenna Fox a...@creativepony.com wrote: I wouldn't bother with reducing the revision number. If anything having weirdly high ones makes the project seem more alive and active. Is the minor number even functionally useful here? Maybe we should ditch that and just keep major as a look! An increment! Heaps cool stuff must have happened! unless google chrome has ruined new major numbers for everyone anyway. Well, it's useful for computability reasons. Every app created on 2.x should work on 2.x+n with minimal required changes. ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Maintenance release of 2.1
True that. Meanwhile, have you guys seen http://twitter.github.com/bootstrap/ ? It looks pretty nice, and I imagine something like that could be pretty powerful if deeply integrated with a version of markaby, as a 'ui toolkit for the web' sort of thing - a nice sensible clean default style for quickly prototyping ideas, and teaching beginners the concepts of the web. — Jenna On 03/10/2011, at 8:47 PM, Magnus Holm wrote: On Sun, Oct 2, 2011 at 14:26, Jenna Fox a...@creativepony.com wrote: I wouldn't bother with reducing the revision number. If anything having weirdly high ones makes the project seem more alive and active. Is the minor number even functionally useful here? Maybe we should ditch that and just keep major as a look! An increment! Heaps cool stuff must have happened! unless google chrome has ruined new major numbers for everyone anyway. Well, it's useful for computability reasons. Every app created on 2.x should work on 2.x+n with minimal required changes. ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Maintenance release of 2.1
Personally I hate it. It's like table border=2 and font size=7 once again, except this time camouflaged as CSS classes. The only good things in there are either styled pretty much the same way by default (like, say, headers), or require a line of code (@basefont, layouts). -- Matma Rex 2011/10/3 Jenna Fox a...@creativepony.com: Meanwhile, have you guys seen http://twitter.github.com/bootstrap/ ? It looks pretty nice, and I imagine something like that could be pretty powerful if deeply integrated with a version of markaby, as a 'ui toolkit for the web' sort of thing - a nice sensible clean default style for quickly prototyping ideas, and teaching beginners the concepts of the web. ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Maintenance release of 2.1
Oh right, but you can use that LESS thing I think to compile the bootstrap properties in to your regular CSS, so you keep using good quality selectors, and bootstrap essentially augments your CSS with useful macros. Another way to do it is to define markaby helpers for each kind of thing, so you can still just go change one small piece of code to restyle the whole site's whizlebobs. — Jenna On 04/10/2011, at 3:07 AM, Bartosz Dziewoński matma@gmail.com wrote: Personally I hate it. It's like table border=2 and font size=7 once again, except this time camouflaged as CSS classes. The only good things in there are either styled pretty much the same way by default (like, say, headers), or require a line of code (@basefont, layouts). -- Matma Rex 2011/10/3 Jenna Fox a...@creativepony.com: Meanwhile, have you guys seen http://twitter.github.com/bootstrap/ ? It looks pretty nice, and I imagine something like that could be pretty powerful if deeply integrated with a version of markaby, as a 'ui toolkit for the web' sort of thing - a nice sensible clean default style for quickly prototyping ideas, and teaching beginners the concepts of the web. ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Maintenance release of 2.1
I'm thinking of releasing 2.1.458 which includes a few more features (better cookie support, inline templates etc), but mainly to fix some incompatibility issues with Rack. I'm not going to document the new features yet, so consider them experimental in this patch-release. As for the version, it's currently MAJOR.MINOR.REV where REV = number of commits since the beginning. It works pretty well to use REV as a part of the version number because I can then easily throw out experimental releases to my gem server without screwing up the version number. However, from 2.2 I'm thinking of changing REV to number of commits since previous release, simply to avoid some high revision numbers. Thoughts? Okay with a little maintenance release? Okay with some undocumented experimental features? Okay with REV? Okay with decreasing REV a bit= // Magnus Holm ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Release?
If 1.5.180 is more stable would it be best to replace 1.5 with 1.5.180 as the 'official' pre-2.0 release for those requiring backward compatibility? If there are 'plenty of bug fixes in the repo', which ones aren't yet incorporated '1.5.180 from _why's gem server which fixes some of them'? I'm kind of speaking as a 'Camping consumer' here - my Ruby's not up to contributing too much. I don't mean to go on about 1.5 (and I'll happily use 2.0 when it's ready), but it would be good to have a solid-as-poss 1.5 version as there are still a lot of examples and working apps out there based around 1.5 (well, nearly all of it is). - Dave Everitt Magnus Holm: Oh, sorry. I totally forgot about this. Are we absolutely sure that 1.5.180 is stable enough to be pushed out to Rubyforge? Julik Tarkhanov: I can, but people who might need my apps can't and won't look for non-official gem servers. Is there a possibility for someone to push the solidified, old-school 1.5.180 to Rubyforge? Before 2.0 is released? It's 2 minutes work, seriously... Magnus Holm: Yes, we should release 2.0 soon... Meanwhile you can always download 2.0 using my repo: gem install camping --source http://gems.judofyr.net/ ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Release?
Totally right :-) It's released now... //Magnus Holm On Thu, Jun 11, 2009 at 01:12, Julik Tarkhanov julian.tarkha...@gmail.comwrote: On 10 Jun 2009, at 23:49, Magnus Holm wrote: Oh, sorry. I totally forgot about this. Are we absolutely sure that 1.5.180 is stable enough to be pushed out to Rubyforge? For about a year I think, and if not it can be followed by 1.5.181 right? -- Julik Tarkhanov m...@julik.nl ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Release?
Oh, sorry. I totally forgot about this. Are we absolutely sure that 1.5.180 is stable enough to be pushed out to Rubyforge? //Magnus Holm On Tue, Feb 10, 2009 at 19:24, Julik Tarkhanov julian.tarkha...@gmail.comwrote: On Feb 10, 2009, at 8:41 AM, Magnus Holm wrote: Yes, we should release 2.0 soon... Meanwhile you can always download 2.0 using my repo: gem install camping --source http://gems.judofyr.net/ I can, but people who might need my apps can't and won't look for non-official gem servers.Is there a possibility for someone to push the solidified, old-school 1.5.180 to Rubyforge? Before 2.0 is released? It's 2 minutes work, seriously... -- Julik Tarkhanov m...@julik.nl ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Release?
On 10 Jun 2009, at 23:49, Magnus Holm wrote: Oh, sorry. I totally forgot about this. Are we absolutely sure that 1.5.180 is stable enough to be pushed out to Rubyforge? For about a year I think, and if not it can be followed by 1.5.181 right? -- Julik Tarkhanov m...@julik.nl ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Getting ready for release
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@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Getting ready for release
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 judo...@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@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Getting ready for release
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? signature.asc Description: This is a digitally signed message part ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Release?
+1 Little wheels, and down the hill :-) Aníbal Rojas http://hasmanydevelopers.com http://rubycorner.com http://anibal.rojas.com.ve On Thu, Feb 12, 2009 at 1:30 AM, Jenna Fox bluebe...@creativepony.com wrote: Yay little wheels! Okay, first task! Whatever Magnus has right now, lets call it 2.0 and release it everywhere! We can bugfix later if we have to. :) On 12/02/2009, at 1:35 PM, _why wrote: On Tue, Feb 10, 2009 at 08:11:46PM +0100, Magnus Holm wrote: Hm... I've always thought 1.5 == 1.5.180... Well, only _why has access to the project, so there's not so much we can do :-( I'm sorry everyone, let's get this all worked out, okay? Magnus, I've added you as an admin on both Rubyforge and Github. And, of course, you are free to add whoever else you like that will help you get your work done. Now, go. Show them Camping is still the little wheels! _why ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Release?
I don't genuinely enjoy using any issue/bug trackers (who does?), but Lighthouse is my least among evils. It's a lot nicer than Trac, anyway. What do you guys think? On Thu, Feb 12, 2009 at 11:40 AM, Magnus Holm judo...@gmail.com wrote: Okay, let's roll! I did some testing with `git checkout` and `diff -r` and figured out that the 1.5.180 gem is revision 173 in the Git repo... Weird stuff... However, let's focus on the future! First of all, we need some plan on how we should name the releases. What about keeping the rev-number in the version number and make it some sort of patchlevel? So 2.0 becomes 2.0.308, and any bugfixes which doesn't change the external API can we release as 2.0.xxx. Should make it simpler to release plain bugfixes without bumping the version number too high. 2.1 would then contain some more new stuff. Should also blend nicely into pre-releases since they can keep the same structure. Documentation is also needed, and we should migrate the old wiki (http://web.archive.org/web/20080107032918/http://code.whytheluckystiff.net/camping) to the github wiki (http://wiki.github.com/why/camping). Maybe some of the wiki-docs should be in the camping-unabridged.rb too... And, we need some place where people can report bugs now when the Trac is gone. Ditz is pretty cool. I could probably set up Sheila too (camping makeup for ditz). Or we could turn this mailing-list into a bugtracker. What do you guys think? Yeah, and I'm going to write a changelog with all the new cool stuff :-) //Magnus Holm On Thu, Feb 12, 2009 at 07:00, Jenna Fox bluebe...@creativepony.com wrote: Yay little wheels! Okay, first task! Whatever Magnus has right now, lets call it 2.0 and release it everywhere! We can bugfix later if we have to. :) On 12/02/2009, at 1:35 PM, _why wrote: On Tue, Feb 10, 2009 at 08:11:46PM +0100, Magnus Holm wrote: Hm... I've always thought 1.5 == 1.5.180... Well, only _why has access to the project, so there's not so much we can do :-( I'm sorry everyone, let's get this all worked out, okay? Magnus, I've added you as an admin on both Rubyforge and Github. And, of course, you are free to add whoever else you like that will help you get your work done. Now, go. Show them Camping is still the little wheels! _why ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Release?
On Feb 12, 2009, at 6:56 PM, Eric Mill wrote: I don't genuinely enjoy using any issue/bug trackers (who does?), but Lighthouse is my least among evils. It's a lot nicer than Trac, anyway. What do you guys think? I rather like the oldskool idea of the bugtracker being powered by Camping itself. Besides, this would move the bugtracker project on it's own. -- Julik Tarkhanov m...@julik.nl ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Release?
On Thu, Feb 12, 2009 at 8:42 PM, Julik Tarkhanov julian.tarkha...@gmail.com wrote: Why not just 2.0.0 with a tag, then 2.0.1 with a tag and so on? Then you also know everytime you release something you have a tag for it. And things like rebases will not ruin your schemes +1 ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Release?
On Feb 10, 2009, at 8:11 PM, Magnus Holm wrote: Hm... I've always thought 1.5 == 1.5.180... Well, only _why has access to the project, so there's not so much we can do :-( I thought so too basically, but it 's not ==, its obviously . Ok, I'll contact him off-list. -- Julik Tarkhanov m...@julik.nl ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Release?
On Tue, Feb 10, 2009 at 08:11:46PM +0100, Magnus Holm wrote: Hm... I've always thought 1.5 == 1.5.180... Well, only _why has access to the project, so there's not so much we can do :-( I'm sorry everyone, let's get this all worked out, okay? Magnus, I've added you as an admin on both Rubyforge and Github. And, of course, you are free to add whoever else you like that will help you get your work done. Now, go. Show them Camping is still the little wheels! _why ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Release?
Yay little wheels! Okay, first task! Whatever Magnus has right now, lets call it 2.0 and release it everywhere! We can bugfix later if we have to. :) On 12/02/2009, at 1:35 PM, _why wrote: On Tue, Feb 10, 2009 at 08:11:46PM +0100, Magnus Holm wrote: Hm... I've always thought 1.5 == 1.5.180... Well, only _why has access to the project, so there's not so much we can do :-( I'm sorry everyone, let's get this all worked out, okay? Magnus, I've added you as an admin on both Rubyforge and Github. And, of course, you are free to add whoever else you like that will help you get your work done. Now, go. Show them Camping is still the little wheels! _why ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Release?
On Feb 10, 2009, at 8:41 AM, Magnus Holm wrote: Yes, we should release 2.0 soon... Meanwhile you can always download 2.0 using my repo: gem install camping --source http://gems.judofyr.net/ I can, but people who might need my apps can't and won't look for non- official gem servers. Is there a possibility for someone to push the solidified, old-school 1.5.180 to Rubyforge? Before 2.0 is released? It's 2 minutes work, seriously... -- Julik Tarkhanov m...@julik.nl ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Release?
Hello folks! Just checking - I understand that Camping 2.0 entered the phase of perpetual polishing and will not likely happen, anytime soon, but would there be a possibility to at least have 1.5.180 on Robyforge for official installs instead of _why's repo? I just tried to deploy my blog just with gem install camping by mistake and been literally plagued by bugs in 1.5.x on forge, including the infamous query-string-params-totally-mixed-with-path-for-R problem and all-my-images-appear-blank problem. Pretty pretty please? -- Julik Tarkhanov m...@julik.nl ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Are we ready for a release ?
On Mar 12, 2008, at 11:16 PM, Jonas Pfenniger wrote: I prefer to state that file uploads doesn't work in CGI instead of penalizing the other adapters. I personally don't really care about CGI. ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Are we ready for a release ?
Hi campers, what do you think of releasing the current trunk as camping-1.6 ? Nothing much has moved since a while and apart from FastCGI, I believe most bugs where ironed out. After the gem release, I propose putting some effort on documentation and how to use Rack's FastCGI. When that's done, we'll have a Rubyforge announcement and such. /me is waiting for community input -- Cheers, Jonas ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Are we ready for a release ?
Hello all, On Wed, Mar 12, 2008 at 05:58:00PM +0100, Jonas Pfenniger wrote: what do you think of releasing the current trunk as camping-1.6 ? Nothing much has moved since a while and apart from FastCGI, I believe most bugs where ironed out. Yeah, I see in the roadmap that there are two bugs open (you mention one here). Are these real blockers? It would be greate to have a relase. After the gem release, I propose putting some effort on documentation and how to use Rack's FastCGI. When that's done, we'll have a Rubyforge announcement and such. Don't forget the tarball release. ;) By the way, do you/we have any release notes, or NEWS listing the new features? Paul -- PhD Student @ Eindhoven | email: [EMAIL PROTECTED] University of Technology, The Netherlands | JID: [EMAIL PROTECTED] Using the Power of Debian GNU/Linux | GnuPG key ID: 0x50064181 ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Are we ready for a release ?
2008/3/12, Paul van Tilburg [EMAIL PROTECTED]: Hello all, On Wed, Mar 12, 2008 at 05:58:00PM +0100, Jonas Pfenniger wrote: what do you think of releasing the current trunk as camping-1.6 ? Nothing much has moved since a while and apart from FastCGI, I believe most bugs where ironed out. Yeah, I see in the roadmap that there are two bugs open (you mention one here). Are these real blockers? It would be greate to have a relase. You're right. Actually the ESPIPE error (#130) is hard to solve. jsheets proposed to read the full upload in a StringIO. That idea clearly doesn't scale to big files. The ideal solution would be to rewrite that big chunk in #initialize to not use IO#revert but I never had the guts to do it. So while I could wait for somebody to do the work, I prefer to state that file uploads doesn't work in CGI instead of penalizing the other adapters. I clearly have to be documented somewhere at least. After the gem release, I propose putting some effort on documentation and how to use Rack's FastCGI. When that's done, we'll have a Rubyforge announcement and such. Don't forget the tarball release. ;) Noted By the way, do you/we have any release notes, or NEWS listing the new features? The changes are only noted in the SVN actually. I'll scan trough it when updating the doc. -- Cheers, Jonas ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
point release?
Hello Esteemed Tent-pitchers, Can we get a point release of the current camping trunk? 1.5.1 maybe? I don't know how stable trunk is, but there are lots of bugs that would be nice to get resolved. Particularly the ones involving the incorrect creation of the sessions table. Evan -- Evan Weaver Cloudburst, LLC ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
RE: point release?
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Evan Weaver Sent: Monday, December 31, 2007 1:27 PM To: Campers Subject: point release? Hello Esteemed Tent-pitchers, Can we get a point release of the current camping trunk? 1.5.1 maybe? I don't know how stable trunk is, but there are lots of bugs that would be nice to get resolved. Particularly the ones involving the incorrect creation of the sessions table. Evan +1 Dan This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: point release?
+ .1 On Dec 31, 2007 2:26 PM, Evan Weaver [EMAIL PROTECTED] wrote: Hello Esteemed Tent-pitchers, Can we get a point release of the current camping trunk? 1.5.1 maybe? I don't know how stable trunk is, but there are lots of bugs that would be nice to get resolved. Particularly the ones involving the incorrect creation of the sessions table. Evan -- Evan Weaver Cloudburst, LLC ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list -- Chris Carter concentrationstudios.com brynmawrcs.com ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Will there be a new release soon?
Hi Daniel, 2007/10/24, Berger, Daniel [EMAIL PROTECTED]: Is there going to be a 1.5.1 release anytime soon? Seems like there have been enough changes in SVN to warrant one and I prefer to use only released code in production. It gives me warmer, fuzzier feelings than using svn/trunk. :) the svn trunk is near the release but still needs some work on the following areas : * better session handling * fastcgi fixes Look in the track for ticket, patches are welcome :) -- Cheers, zimbatm ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Will there be a new release soon?
Hi all, the svn trunk is near the release but still needs some work on the following areas : * better session handling * fastcgi fixes this time I need both of them (with a Remember me function) ;) Greetings, Bence -- Nagy Bence - Tipográl | www.tipogral.hu - Tipokert | www.tipokert.hu - Dekk | www.dekk.hu - Magyar Grafika | www.mgonline.hu - Hírkapu | www.hirkapu.hu ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: WEBrick Re: Next camping release
2007/9/27, Ernest Prabhakar [EMAIL PROTECTED]: I was looking at the test cases on the changeset: http://code.whytheluckystiff.net/camping/browser/trunk/test?rev=227 However, I didn't see anything about testing with different web browsers; which is a concern since there was a nasty WEBrick bug in the last version. Is there test coverage for that? Hi Ernie, I didn't get into testing the various web servers yet. Ref 277 is the base to do that, since those apps can be tested against the various web servers. I know there are some issues with FastCGI too so I'll have to get into it anyways. P.S. I mean to file the bug, but got into a fight with the trac system. ;-( You need a http://rubyforge.org/ account, which you can then reuse here : http://code.whytheluckystiff.net/access/ Once you are registered, you can log into the various Trac applications. File upload doesn't work tough. Anyways, you can still describe your bug on the list and I'll see what to do. -- Cheers, zimbatm ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: WEBrick Re: Next camping release
On Sep 27, 2007, at 10:44, Jonas Pfenniger wrote: P.S. I mean to file the bug, but got into a fight with the trac system. ;-( Patch uploads seem to be broken, so maybe _why can have a look-see? Manfred ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
WEBrick Re: Next camping release
Hi all, I was looking at the test cases on the changeset: http://code.whytheluckystiff.net/camping/browser/trunk/test?rev=227 However, I didn't see anything about testing with different web browsers; which is a concern since there was a nasty WEBrick bug in the last version. Is there test coverage for that? -- Ernie P. P.S. I mean to file the bug, but got into a fight with the trac system. ;-( ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Next camping release
2007/9/25, Michael Maltese [EMAIL PROTECTED]: That makes sense. An extension, do you mean like camping/session? Yes, and the gem dependency would only be added to camping-omnibus. But first, let's release Camping 1.6 -- Cheers, zimbatm ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Next camping release
2007/9/25, Michael Maltese [EMAIL PROTECTED]: Remove Markaby? How will that work? Only as a direct dependency. It will probably kept as an extension. Basically, you can return a string containing html from your controller methods even if it's a bit rough. -- Cheers, zimbatm ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Next camping release
Dear camping users, having been contacted by Julian Tarkhanov, I am willing to prepare the next camping release. _why has given me his friendly approval, with the reserve that camping.rb should be lower than 4k. He also told me that he wanted to remove the ActiveSupport and Markaby dependencies. I am writing here to get the users input so that I don't do any mistake. So far, my plans are to : - solve all remaining bugs in the tracker - remove the unused #errors_for method. Please give some input if you do ! - add some unit-tests. This will result in a short-term release with not too much changes, used for code stabilization. When this is done, I will embark on 2.0 for bigger changes like Markaby and AR removal. Cheers, zimbatm ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Next camping release
it would be really cool do remove the apache scriptAlias directive so camping would run everywhere On 9/23/07, Manfred Stienstra [EMAIL PROTECTED] wrote: This will result in a short-term release with not too much changes, used for code stabilization. When this is done, I will embark on 2.0 for bigger changes like Markaby and AR removal. Cool, I'm currently trying to get my apps working with svn camping. I think I've found a problem surrounding URL(). Jonas, can you try to float around #camping to discuss any problems? Manfred ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list -- André G. Cardozo ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
Re: Next camping release
2007/9/23, Manfred Stienstra [EMAIL PROTECTED]: This will result in a short-term release with not too much changes, used for code stabilization. When this is done, I will embark on 2.0 for bigger changes like Markaby and AR removal. Cool, I'm currently trying to get my apps working with svn camping. I think I've found a problem surrounding URL(). Jonas, can you try to float around #camping to discuss any problems? I am not really an IRC user but I will try to. I'd really appreciate if every concerned person could follow the changesets and raise objection on the list. It is easy to follow if you use rss feeds : http://code.whytheluckystiff.net/camping/timeline?milestone=onticket=onchangeset=onwiki=onmax=50daysback=90format=rss -- Cheers, zimbatm ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list
