To keep the tested styles in the master branch is certainly possible. In fact, this is similar to our current test setup, as we created separate branches for the Ruby and Python tests respectively. It is then very easy to configure travis-ci to run the tests on a specific branch only.
By the way, I just pulled in the latest styles from the master branch and all tests are passing now. Rintze, if you give me write access to the official wiki I will add instructions on how to set up the test environment there. Sylvester On Jul 17, 2012, at 2:23 AM, Charles Parnot wrote: > We can definitely arrange it any way we want. I can see how it would make > sense that the master branch of the main CSL repository would have the full > tested styles and would be the one clients should pull from, and users could > download from. > > An 'edge' branch or fork would be the one with the commits still to be tested. > > charles > > > On Jul 16, 2012, at 4:48 PM, Bruce D'Arcus wrote: > >> Been out of town, and will look at this more closely later. But my strong >> belief is that (in particular the master branch on) the main csl style repo >> should be the canonical one. Is that not possible? >> >> On Jul 16, 2012 5:12 PM, "Robert Knight" <[email protected]> wrote: >> Hello, >> >> Thanks Rintze and Sylvester for working on this. It should make it >> easier for us to safely provide frequent style updates to users. >> >>> ii) create a separate repository that automatically pulls in commits from >>> https://github.com/citation-style-language/styles, >>> but only if all tests pass. I think this should be relatively easy to set >>> up with a commit hook, and should be very maintenance free. >>> Consumers of CSL styles could then get their styles from that verified >>> repository. >> >> This seems sensible and matches our own workflow internally - except >> that we apply commit restrictions (which can be on the committer, the >> content of the commit message or the content blobs) only to certain >> branches in the pre-receive hook rather than the whole repository. >> >> Though git makes it easier to push, pull and merge between different >> repositories, I suspect that just applying restrictions on pushing to >> certain branches (eg. only the CI system can push to master) might be >> easier to work with. >> >> Regards, >> Rob. >> >> On 16 July 2012 21:43, Charles Parnot <[email protected]> wrote: >>>>> Could we merge this now into the main repository, so we can start using >>>>> it? Maybe with a few instructions? I like the idea of having those tests >>>>> right there with the repo. And it will then be possible for us to submit >>>>> more tests or modify existing ones if needed. >>>> Yes, that was another question that slipped my mind. Does anybody object >>>> to putting the test scripts in the main repo? >>> >>> If possible, it would be nice to move all the related files inside one >>> directory, e.g. /Tests/? >>> >>> >>>> Sylvester helped me along running the tests locally on Windows XP (through >>>> http://rubyinstaller.org/ ), which was a quick setup. >>> >>> Looks like I will just need to install a few gems, then. >>> >>> 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 >> ------------------------------------------------------------------------------ >> 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
signature.asc
Description: Message signed with OpenPGP using GPGMail
------------------------------------------------------------------------------ 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
