[01:23:07] *** Quits: Horwitz (~mich1@p200300ec9f069400022268fffe64e7c4.dip0.t-ipconnect.de) (Ping timeout: 272 seconds)
[01:35:24] *** Joins: Horwitz (~mich1@p200300ec9f024100022268fffe64e7c4.dip0.t-ipconnect.de)
[01:35:24] *** ChanServ sets mode: +o Horwitz
[02:42:56] *** Quits: Cyker (~Cyker@host-92-28-109-119.as13285.net) (Ping timeout: 240 seconds)
[02:56:04] *** Joins: Cyker (~Cyker@80-44-162-3.dynamic.dsl.as9105.com)
[04:42:49] *** Quits: Cyker (~Cyker@80-44-162-3.dynamic.dsl.as9105.com) (Ping timeout: 264 seconds)
[04:49:59] *** Joins: Cyker (~Cyker@81-178-218-85.dsl.pipex.com)
[11:04:26] <Navit> <ilovekiruna> @jkoan , I just cmae up with another idea for the versionCode
[11:04:51] <Navit> <jkoan> Yes? :d
[11:04:59] <Navit> <jkoan> * :D
[11:04:59] <Navit> <ilovekiruna> what about just making the last two digits a running index
[11:05:01] <Navit> <ilovekiruna> in the hour
[11:05:31] <Navit> <ilovekiruna> then you could relase 100 releases per hour
[11:06:51] <Navit> <jkoan> This is how it's today? HHmm but this has to many digits
[11:07:05] <Navit> <jkoan> Or do I misunderstood something?
[11:07:43] <ilovekiruna> maybe I wrote it a bit wrong
[11:09:03] <ilovekiruna> or just running index per day
[11:09:21] <ilovekiruna> so yyyyMMddXX
[11:09:48] <ilovekiruna> do we really have so many releases in a day?
[11:11:31] <Navit> <jkoan> We don't have so many but it's a question about how it's calculated and we (or I) decided about a time based versioncode. And if two commits are falling in the same timeframe this is a problem
[11:12:19] <ilovekiruna> and this problem can be avoided if one diverts from a strictly time based version code
[11:12:26] <ilovekiruna> just a thought
[11:12:56] <Navit> <jkoan> But where do keep the index? The build is distributed
[11:14:14] <Navit> <ilovekiruna> is there a way to get the latest version on google play?
[11:17:33] <Navit> <jkoan> Maybe, but this isn't a hoot source of through because it can also have a error, be unavailable or whatever. Maybe a plain text file could be a solution which can be cached between builds, but this would add additional complexity to the build, which I want to avoid
[11:20:47] <Navit> <ilovekiruna> I understand the concern
[11:21:11] <Navit> <ilovekiruna> one more question on the previous calculation
[11:21:19] <Navit> <ilovekiruna> can there be number clashes?
[11:23:50] <Navit> <ilovekiruna> so could  there be any non-unique combinations of dd HH and mm?
[14:32:15] *** Quits: ilovekiruna (~ilovekiru@ip1f129c09.dynamic.kabel-deutschland.de) (Quit: Konversation terminated!)
[15:14:25] <Navit> <jkoan> I will make a test for that this afternoon
[19:14:07] <Navit> <jkoan> @ilovekiruna i verified that there is no collosion
[19:14:26] <Navit> <jkoan> (ofer than only every 15min)
[21:51:14] *** Joins: peterm6881 (~Peter@91.40.93.209.dyn.plus.net)
[22:11:54] *** Joins: ilovekiruna (~ilovekiru@ip1f129c09.dynamic.kabel-deutschland.de)
[22:11:54] *** ChanServ sets mode: +v ilovekiruna