Or we (and you) can add those CHANGES also. It's not that hard if you've reviewed the commits anyway and everything should not end up in CHANGES anyway (i mean, who cares that CVS revisions have been removed from the files, for example) so i think that it's not that good idea to force it or anything. Just saying that it's easier to keep it up to date right now than start filling in the gaps later.
Jarmo On Wed, Oct 6, 2010 at 9:18 PM, Bret Pettichord <b...@pettichord.com> wrote: > This is good advice, which I know I need to follow as well. > > To help get us to be more disciplined, let's all agree not to merge in pull > requests that don't include appropriate updates to CHANGES. > > Bret > > On Wed, Oct 6, 2010 at 10:08 AM, Jarmo <jarm...@gmail.com> wrote: >> >> Hi! >> >> I've noticed quite many pull requests and merges lately (mostly made >> by Ċ½eljko). I'd like to remind all of you that it would be easier to >> add those things into CHANGES right now than later. Especially these >> changes which might affect end user (like deleting watir-simple) and >> so on. >> >> Jarmo >> _______________________________________________ >> Wtr-development mailing list >> Wtr-development@rubyforge.org >> http://rubyforge.org/mailman/listinfo/wtr-development > > > -- > Bret Pettichord > Lead Developer, Watir, www.watir.com > > Blog, www.io.com/~wazmo/blog > Twitter, www.twitter.com/bpettichord > > > _______________________________________________ > Wtr-development mailing list > Wtr-development@rubyforge.org > http://rubyforge.org/mailman/listinfo/wtr-development > _______________________________________________ Wtr-development mailing list Wtr-development@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-development
