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 me at julik.nl
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 <julian.tarkhanov at gmail.com> wrote:> 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 > me at julik.nl > > > > > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list
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 me at julik.nl -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/camping-list/attachments/20090210/b24ea383/attachment.html>
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 <julian.tarkhanov at gmail.com>wrote:> > 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 > me at julik.nl > > > > > > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/camping-list/attachments/20090210/d2f0a47a/attachment.html>
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 me at julik.nl
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
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 at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list
+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 <blueberry at 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 at rubyforge.org >> http://rubyforge.org/mailman/listinfo/camping-list > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list >
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 <blueberry at 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 at rubyforge.org >> http://rubyforge.org/mailman/listinfo/camping-list >> > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/camping-list/attachments/20090212/8a4c35ae/attachment.html>
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 <judofyr at 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 <blueberry at 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 at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/camping-list >> >> _______________________________________________ >> Camping-list mailing list >> Camping-list at rubyforge.org >> http://rubyforge.org/mailman/listinfo/camping-list > > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list >
On Feb 12, 2009, at 5:40 PM, Magnus Holm wrote:> However, let''s focus on the future! First of all, we need some plan > on how we should name the releases.Basic. http://www.rubygems.org/read/chapter/7 Knowing how much changed on 2.0 I expect that some things are very different and analogous 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 make it > some sort of "patchlevel"?What worked well for me is upping the "tiny" revision every time I say "this is a tagged release, and it goes out to rubyforge". Putting int SHAs in there doesn''t really scale because less has to still mean "older" and more has to mean "younger".> 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.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 -- Julik Tarkhanov me at julik.nl
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 me at julik.nl
On Thu, Feb 12, 2009 at 8:42 PM, Julik Tarkhanov <julian.tarkhanov at 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
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.tarkhanov at gmail.com>wrote:> > 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 > me at julik.nl > > > > > > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/camping-list/attachments/20090610/f416c7ac/attachment.html>
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 me at julik.nl
Totally right :-) It''s released now... //Magnus Holm On Thu, Jun 11, 2009 at 01:12, Julik Tarkhanov <julian.tarkhanov at gmail.com>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? >> > > > For about a year I think, and if not it can be followed by 1.5.181 right? > -- > Julik Tarkhanov > me at julik.nl > > > > > > _______________________________________________ > Camping-list mailing list > Camping-list at rubyforge.org > http://rubyforge.org/mailman/listinfo/camping-list >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/camping-list/attachments/20090611/2d6ab4b1/attachment.html>
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/