Re: The 2.2 release

On Thu, Oct 09, 2014 at 10:31:50PM +0200, Sebastjan Hribar wrote: > I have no issues with AR 4.0.4. I also had to make some minor adjustments > and that's it. I use 4.1.6, saw you had problems with it, but I didn't. Maybe I need to try the migrations. Paul -- Web: http://paul.luon.net/home/

Re: The 2.2 release

Hi Paul, I have no issues with AR 4.0.4. I also had to make some minor adjustments and that's it. regards, seba On 08. 10. 2014 21:10, Paul van Tilburg wrote: 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, wh

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 q

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

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 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 >

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

Re: Camping release?

Hi Paul (and senior Campers) the public Camping gem is at 2.1.467. I can't recall (without trawling the mailing list) all the details of discussions about proposed changes/issues addressed, so just to clarify: where did decisions about 2.2 get to? Personally (and running a Debian server)

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 fo

Re: Camping release?

h 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

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 ad

Re: Camping 2.2 pre-release

failing test case, running in camping: def layout text "\n" html { head { title "foo" } } end Markaby output: foo Mab output: foo — Jenna Fox On Wednesday, 25 January 2012 at 10:00 PM, Magnus Holm wrote: > gem install camping --source http://gems.judofyr.net/ ___

Camping 2.2 pre-release

gem install camping --source http://gems.judofyr.net/ *wonders how much Mab breaks* // Magnus Holm ___ 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 ca

Re: Maintenance release of 2.1

Personally I hate it. It's like and 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 : > Meanwhile

Re: Maintenance release of 2.1

True that. Meanwhile, have you guys seen ? 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 fo

Re: Maintenance release of 2.1

On Sun, Oct 2, 2011 at 14:26, Jenna Fox 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 "loo

Re: Maintenance release of 2.1

e > 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

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 t

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 ge

Re: Release?

Awesome. On 11 Jun 2009, at 15:16, Magnus Holm wrote: Totally right :-) It's released now... //Magnus Holm On Thu, Jun 11, 2009 at 01:12, Julik Tarkhanov > wrote: 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 s

Re: Release?

Totally right :-) It's released now... //Magnus Holm On Thu, Jun 11, 2009 at 01:12, Julik Tarkhanov wrote: > > 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? >

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 _

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 wrote: > > On Feb 10, 2009, at 8:41 AM, Magnus Holm wrote: > > Yes, we should rele

Re: Getting ready for release

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 t

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/). Wha

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/). Wha

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

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.

Re: Release?

On Thu, Feb 12, 2009 at 8:42 PM, Julik Tarkhanov 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 sc

Re: Release?

ogous to API change, so 2.0 be it. 1.5.180 is just "tiny" 180 and a bugfix release, besides people who installed it from _why's server will not get screwed when it pops up on their server and they set it up as a dep. What about keeping the rev-number in the version number and

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 its

Re: Release?

e 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

Re: Release?

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

Re: Release?

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

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 though

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 Rubyforg

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...@j

Re: Release?

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 :-( //Magnus Holm On Tue, Feb 10, 2009 at 18:24, Julik Tarkhanov wrote: > > On Feb 10, 2009, at 8:41 AM, Magnus Holm wrote: > > Yes, we s

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 s

Re: Release?

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/ //Magnus On 10. feb.. 2009, at 06.50, Julik Tarkhanov wrote: Hello folks! Just checking - I understand that Camping 2.0 entered the phase of

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 j

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.or

Re: Are we ready for a release ?

On 3/12/08, Jonas Pfenniger <[EMAIL PROTECTED]> wrote: > 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 rele

Re: Are we ready for a release ?

On Mar 12, 2008, at 10:58 AM, Jonas Pfenniger wrote: > 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 propos

Re: Are we ready for a release ?

2008/3/12, Jonas Pfenniger <[EMAIL PROTECTED]>: > 2008/3/12, Paul van Tilburg <[EMAIL PROTECTED]>: > > 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

Re: Are we ready for a release ?

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 > > R

Re: Are we ready for a release ?

e 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 an

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&#

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 g

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 th

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 --

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

Re: Will there be a new release soon?

On Tue, Nov 06, 2007 at 06:15:53PM +0100, Jonas Pfenniger wrote: > 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 :) Let's call thi

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 feelin

Will there be a new release soon?

Hi, 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. :) Regards, Dan This communication is the propert

Re: WEBrick Re: Next camping release

Hi Jonas, On Sep 27, 2007, at 1:44 AM, Jonas Pfenniger wrote: > 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 any

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@

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 WEB

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 c

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 --

Re: Next camping release

That makes sense. An extension, do you mean like camping/session? On 9/24/07, Jonas Pfenniger <[EMAIL PROTECTED]> wrote: > > 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,

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 ___

Re: Next camping release

Remove Markaby? How will that work? ___ Camping-list mailing list Camping-list@rubyforge.org http://rubyforge.org/mailman/listinfo/camping-list

Re: Next camping release

2007/9/24, andré gustavo cardozo <[EMAIL PROTECTED]>: > it would be really cool do remove the apache scriptAlias directive so > camping would run everywhere Sure, could you file a bug for this ? -- Cheers, zimbatm ___ Camping-list mailing list Campin

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. >

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. > > &g

Re: Next camping release

> 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

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

Re: [ANN] TentSteak First Release

Aredridel wrote: John Sheets wrote: Hey all, I just pushed out the inaugural release of TentSteak 0.1.0, a set of Camping/Markaby helpers to minimize the busywork in your views (or was that the "viewwork in your busies"?). It includes lotsa HTML form and table helpers, plu

Re: [ANN] TentSteak First Release

John Sheets wrote: > Hey all, > > I just pushed out the inaugural release of TentSteak 0.1.0, a set of > Camping/Markaby helpers to minimize the busywork in your views (or was > that the "viewwork in your busies"?). It includes lotsa HTML form and > table helpers, p

[ANN] TentSteak First Release

Hey all, I just pushed out the inaugural release of TentSteak 0.1.0, a set of Camping/Markaby helpers to minimize the busywork in your views (or was that the "viewwork in your busies"?). It includes lotsa HTML form and table helpers, plus a little bootstrapper to make it easy to