On Tue, Feb 24, 2009 at 5:58 PM, Kero van Gelder wrote:
>> > I find pushing last thing at night even more bizarre to be honest :/
>> > If you're are going home, it seems reasonable that other people might
>> > be, ergo there won't be many more changes made (an assumption
>> > granted). Also, if th
Hey, if you're using Fixjour, you might be interested in its new
mailing list - http://groups.google.com/group/fixjour. If you're not
using Fixjour, you should be.
Pat
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/l
> > I find pushing last thing at night even more bizarre to be honest :/
> > If you're are going home, it seems reasonable that other people might
> > be, ergo there won't be many more changes made (an assumption
> > granted). Also, if they are going to continue to work and make
> > changes, why fo
Kero van Gelder wrote:
If you redo a product, you have learned what it should look like.
Thus, you can specify much more in advance. Nothing wrong with that,
it came out of the feedback loops.
Here's pure Waterfall (phase 2, not 3 of his project):
"7 reasons I switched back to PHP after 2 yea
On 24 Ún, 17:26, Nick Hoffman wrote:
> On 24/02/2009, at 8:03 AM, vo.x wrote:
>
>
>
> > On 23 Ún, 18:41, Nick Hoffman wrote:
> >> On 22/02/2009, at 3:34 PM, vo.x wrote:
>
> >>> Hello all,
>
> >>> Is there some best practice how to test Rails controller action
> >>> which
> >>> is using send_fil
>> yeah, you guys are probably right on this. I was just over stating. :)
>
> Ah, but Waterfall is indeed like the Emissaries of the Shadow. If you
> defeat one of them, in one form, another one will always appear, take
> shape, and grow...
>
> I myself have heard well-meaning product managers sa
On Tue, Feb 24, 2009 at 10:56 AM, Pat Maddox wrote:
>
> Much better to rebase -i to clean up a bunch of little commits, imo.
> Gives you all the flexibility in the world when developing, then when
> you're ready to share you can assemble nice independent, meaningful
> changes.
Yeah, I use rebase
On Tue, Feb 24, 2009 at 10:16 AM, Mark Wilden wrote:
> On Tue, Feb 24, 2009 at 1:17 AM, Matt Wynne wrote:
>>
>> See particularly the notes about squashing commits - this allows you to
>> commit really often in your local branch, then merge these commits together
>> before you push them into the m
On Tue, Feb 24, 2009 at 1:16 PM, Mark Wilden wrote:
>
> Another workflow (which I don't personally use) is to continually git
> commit --amend, changing the commit message each time. This avoids the
> rebase step before pushing, but of course you don't have the
> checkpoints.
Egad. Why am I remi
On Tue, Feb 24, 2009 at 1:17 AM, Matt Wynne wrote:
>
> See particularly the notes about squashing commits - this allows you to
> commit really often in your local branch, then merge these commits together
> before you push them into the main source control repository.
>
> You can even use git comm
Stephen Eley wrote:
> It is an interesting idea. I knew Redmine had wiki and forum
> features. I think I've probably been somewhat unfair to it because I
> got the sense it was trying to be a better Trac, and Trac leaves a bad
> taste in my mouth. I know that's not rational, and I should give i
I was trying to use intergration and commit to be specific scm terms in this
sort of discussion, so rephrasing (and hopefully improving on ) Dave
Laribee's law we get
"If its late in the day save your next integration for the morning"
Now people can go home on time and not fret about a build brea
On Tue, Feb 24, 2009 at 10:11 AM, James Byrne wrote:
>
> I am sorry that I did not make myself clearer. Redmine is far more than
> a project management tool. It is in fact a rather sophisticated, if
> limited, content management tool that supports PostgreSQL as its back
> end. I was suggesting
Andrew Premdas wrote:
> James,
...
> Client is not a good name for an emphemeral role. If you need adverbs
> and adjectives to clarify your verbs and nouns, then your verbs and nouns
> aren't good enough. I'm not convinced that Entity is a particularly good
> name either the fact that you need so
On 24/02/2009, at 8:03 AM, vo.x wrote:
On 23 Ún, 18:41, Nick Hoffman wrote:
On 22/02/2009, at 3:34 PM, vo.x wrote:
Hello all,
Is there some best practice how to test Rails controller action
which
is using send_file method? Could you help me please?
Vit
On 23/02/2009, at 2:43 AM, vo.
On Tue, Feb 24, 2009 at 9:47 AM, Rob Holland wrote:
>
> I find pushing last thing at night even more bizarre to be honest :/
> If you're are going home, it seems reasonable that other people might
> be, ergo there won't be many more changes made (an assumption
> granted). Also, if they are going t
Stephen Eley wrote:
>
> Thanks, James. But at the moment I have no need for that level of
> overhead. Gantt charts are an anti-feature for me. I'm effective
> enough with my index cards and thumbtacks. >8->
>
I am sorry that I did not make myself clearer. Redmine is far more than
a projec
On 24 Feb 2009, at 15:23, aslak hellesoy wrote:
I find pushing last thing at night even more bizarre to be honest :/
Completely agree. Ending the day with a git push / svn commit is
verboten where I work. Dave Laribee describes why in biblical form:
http://codebetter.com/blogs/david_laribee/a
On Tue, Feb 24, 2009 at 3:47 PM, Rob Holland wrote:
>> Because the longer you wait, the more your code will diverge from your
>> teammates'. If you don't commit often you rob them of the opportunity
>> to reduce merge hell.
>
> Please note I did say commit, and not push, and I inferred from Matt
>
> Because the longer you wait, the more your code will diverge from your
> teammates'. If you don't commit often you rob them of the opportunity
> to reduce merge hell.
Please note I did say commit, and not push, and I inferred from Matt
he meant commit and not push (although he has explained othe
Stephen Eley wrote:
> What can you learn from that? Taken in isolation, without knowing
> anything more, could you compute the value of the Web site to the
> organization? Could you tell me what the feature count is likely to
> be?
I do not know what the actual feature count and scenario count
On Tue, Feb 24, 2009 at 10:30 AM, Rob Holland wrote:
> On Tue, Feb 24, 2009 at 9:17 AM, Matt Wynne wrote:
>
>> You can even use git commit --amend to commit on red (e.g at the end of the
>> day) and then change that commit later.
>
> While I think commit --amend is very useful, I'm not sure why y
On 23 Ún, 18:41, Nick Hoffman wrote:
> On 22/02/2009, at 3:34 PM, vo.x wrote:
>
> > Hello all,
>
> > Is there some best practice how to test Rails controller action which
> > is using send_file method? Could you help me please?
>
> > Vit
>
> On 23/02/2009, at 2:43 AM, vo.x wrote:
>
> > Just to b
Matt Wynne wrote:
I take my laptop home on the bus through central London
Got WiFi?
--
Phlip
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
>David Chelimsky
>That may be so, but one view of agile is that each iteration is a
>mini-waterfall. BDD suggests that we *should* define all of the
>scenarios in the iteration planning meeting because we use them as a
>planning tool (how can we estimate a feature at all before we've
>talked about
On 24 Feb 2009, at 09:30, Rob Holland wrote:
On Tue, Feb 24, 2009 at 9:17 AM, Matt Wynne
wrote:
You can even use git commit --amend to commit on red (e.g at the
end of the
day) and then change that commit later.
While I think commit --amend is very useful, I'm not sure why you'd
bother
On Tue, Feb 24, 2009 at 9:17 AM, Matt Wynne wrote:
> You can even use git commit --amend to commit on red (e.g at the end of the
> day) and then change that commit later.
While I think commit --amend is very useful, I'm not sure why you'd
bother to commit at the end of the day, knowing full well
On 19 Feb 2009, at 03:36, Michael Sofaer wrote:
I'm trying to set my request body in my tests (the application is a
web service that takes large XML files in PUT requests).
If you do this:
put :update, :body => xml
You get a request with an empty body, and a field in the header called
"body"
On 23 Feb 2009, at 00:09, Yi Wen wrote:
Wait for an hour before I can checkin something is still too long
for me. I'd like to checkin every couple minutes most of time.
But I think to make each step just pending first and then make it
green when I finish implementation for the step makes s
29 matches
Mail list logo
