That makes sense to me. But then if that's the case, we don't need to test on master; do we (unless we're not confident people will only work on "development")?
On Thu, Jul 19, 2012 at 5:40 PM, Charles Parnot <[email protected]> wrote: > My understanding is this: > > Styles changes are pushed by controbutors to the 'development' branch. This > triggers a Travis CI run. If the tests succeed, the corresponding commit is > fast-forwarded on the 'master' branch. > > > > On Jul 19, 2012, at 2:38 PM, Bruce D'Arcus wrote: > >> Well, before we settle this, what's the workflow we're imagining for adding >> style changes? >> >> On Jul 19, 2012 5:21 PM, "Charles Parnot" <[email protected]> wrote: >> > I don't think there's a real downside to running the tests on master, as >> > well, unless we are concerned about the additional clutter caused by the >> > test files. If not the tests, it seems we will have to at least add the >> > .travis.yml file to make sure that travis sees our configuration. (I'm >> > travelling at the moment so I can't look at this until later this >> > weekend.) And you're right that *not* adding the tests will become a >> > nuisance if we want to merge development with master down the road. >> >> OK! Now, is there any simple way to "hide" the tests inside a subfolder in >> the repository? If easy, then maybe it's worth the extra effort to keep the >> file layout "clean"? >> >> Thanks again so much for this work, this is exactly what we have been needed >> for a while! >> >> charles >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> xbiblio-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. >> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/_______________________________________________ >> xbiblio-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/xbiblio-devel > > -- > Charles Parnot > [email protected] > twitter: @cparnot > http://mekentosj.com > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > xbiblio-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/xbiblio-devel ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
