Let's also take this into a new thread. There are a lot of different
conversations now going on
On Fri, Mar 7, 2014 at 9:21 AM, Brad Jorsch (Anomie)
bjor...@wikimedia.org wrote:
On Fri, Mar 7, 2014 at 12:08 PM, C. Scott Ananian
canan...@wikimedia.orgwrote:
I agree. I think a better
On Fri, Mar 7, 2014 at 10:30 AM, Jon Robson jdlrob...@gmail.com wrote:
Let's also take this into a new thread. There are a lot of different
conversations now going on
On Fri, Mar 7, 2014 at 9:21 AM, Brad Jorsch (Anomie)
bjor...@wikimedia.org wrote:
On Fri, Mar 7, 2014 at 12:08 PM, C.
quote name=Jon Robson date=2014-03-07 time=09:30:09 -0800
Let's also take this into a new thread. There are a lot of different
conversations now going on
My opinion is that fixing this with policy is going to be hard.
Either everyone who commits needs to be mindful of what day/time it is
I feel like I should probably post here about the current Wikibase /
Wikidata deployment pipeline too which probably differs slightly to other
products.
On a per commit basis:
A commit is made, the unit tests run on jenkins, the commit is reviewed,
amended, merged, Jenkins again runs the unit
One thing I didn't mention is that we recently marked a few of our selenium
tests as smoke tests which I just spotted was suggested in the other email
thread for core!
Great idea!
Addshore
On 7 March 2014 19:34, addshorewiki addshorew...@gmail.com wrote:
I feel like I should probably post
On 03/07/2014 10:08 AM, Greg Grossmeier wrote:
What we should do, however, is have a true deployment pipeline.
Briefly defined: A deployment pipeline is a sequence of events that
increase your confidence in the quality of any particular build/commit
point.
A typical example is:
commit -
