Perl 6 - the future is here, just unevenly distributed

IRC log for #gluster-dev, 2014-09-22

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
02:19 bala joined #gluster-dev
03:05 hchiramm_ joined #gluster-dev
03:26 kshlm joined #gluster-dev
03:43 bharata-rao joined #gluster-dev
03:53 itisravi joined #gluster-dev
04:08 kdhananjay joined #gluster-dev
04:16 atinmu joined #gluster-dev
04:22 ndarshan joined #gluster-dev
04:33 bala joined #gluster-dev
04:37 Rafi_kc joined #gluster-dev
04:37 rafi1 joined #gluster-dev
04:40 anoopcs joined #gluster-dev
04:42 anoopcs1 joined #gluster-dev
04:47 anoopcs joined #gluster-dev
05:01 jiffin joined #gluster-dev
05:07 kanagaraj joined #gluster-dev
05:11 spandit joined #gluster-dev
05:23 aviksil joined #gluster-dev
05:31 hagarth joined #gluster-dev
05:32 ppai joined #gluster-dev
05:33 Gaurav_ joined #gluster-dev
05:53 deepakcs joined #gluster-dev
06:05 atalur joined #gluster-dev
06:14 soumya__ joined #gluster-dev
06:30 lalatenduM joined #gluster-dev
06:35 deepakcs joined #gluster-dev
07:10 deepakcs joined #gluster-dev
07:22 atinmu joined #gluster-dev
07:23 raghu joined #gluster-dev
07:32 hagarth joined #gluster-dev
07:49 atinmu joined #gluster-dev
07:57 nishanth joined #gluster-dev
08:04 hagarth joined #gluster-dev
08:29 bala joined #gluster-dev
08:37 RaSTar joined #gluster-dev
08:38 RaSTar joined #gluster-dev
08:40 ndevos hagarth: should I move all bugs that should be fixed with glusterfs-3.6.0beta1 to ON_QA ?
08:41 hagarth ndevos: that would be great
08:42 ndevos hagarth: is there a public announcement somewhere, that I can link from the bug report on updating?
08:44 hagarth ndevos: http://supercolony.gluster.org/pipermail/gluster-devel/2014-September/042326.html ?
08:44 ndevos hagarth: yeah, I'd use that if there is nothing more verbose :)
08:45 hagarth ndevos: unfortunately nothing much atm, I intend to push out a blog post soon
08:46 ndevos hagarth: okay, I'll use the Jenkins email then :)
08:46 hagarth ndevos: cool, thanks :)
08:50 bala joined #gluster-dev
09:02 soumya__ joined #gluster-dev
09:12 vikumar joined #gluster-dev
09:13 hagarth joined #gluster-dev
09:18 hagarth kshlm: ping, can you please help with review of http://review.gluster.org/8292 ?
09:21 soumya__ joined #gluster-dev
09:52 ws2k333 joined #gluster-dev
09:57 nishanth joined #gluster-dev
10:32 nishanth joined #gluster-dev
10:49 hagarth joined #gluster-dev
10:58 hagarth raghu: ping, need some help with uss
11:13 krishnan_p joined #gluster-dev
11:26 ppai joined #gluster-dev
11:47 soumya_ joined #gluster-dev
12:03 ira joined #gluster-dev
12:06 bala joined #gluster-dev
12:19 itisravi_ joined #gluster-dev
12:29 edward1 joined #gluster-dev
12:40 ndevos hagarth: fyi, I'm marking 362 bugs ON_QA/3.6.0beta1 now :)
12:40 hagarth ndevos: awesome!
12:44 hagarth ndevos: that also explains the mail bomb i am going through now ;)
12:45 ndevos hagarth: that can well be, and the script is still running...
12:45 * ndevos checks emails every 30 minutes, and will get bombed soon too
12:47 kshlm Should be done now.
12:47 kshlm Just counted 360 new messages from  bugzilla.
12:50 ndevos indeed, seems finished - now go and test!
12:56 * hagarth tests and moves 360 bugs from ON_QA to VERIFIED
13:07 RaSTar joined #gluster-dev
13:08 soumya_ joined #gluster-dev
13:23 hagarth joined #gluster-dev
13:28 ndevos JustinCl1ft: how about blog/syncing http://blog.nixpanic.net/2014/09/experimenting-with-ceph-support-for-nfs.html ?
13:28 ndevos :P
13:32 JustinCl1ft ndevos: Hmmm, I thought it was supposed to do that automatically
13:32 * JustinCl1ft goes and presses buttons
13:32 ndevos JustinCl1ft: it is, as long as I add the Gluster tag, which I did not do in this case - not sure if it should get sync'd
13:33 JustinCl1ft Yeah, not in this case
13:40 shyam joined #gluster-dev
13:44 bala joined #gluster-dev
14:50 kshlm joined #gluster-dev
14:51 kshlm joined #gluster-dev
14:52 lalatenduM kkeithley, regarding pushing 3.6beta spec file to fedora dist git
14:53 lalatenduM kkeithley, I think we should not commit these changes to dist git till we release of 3.6GA as , I think we should push 4.5.3 in fedora when it is released
15:03 lalatenduM kkeithley, thanks for rearranging the sections kkeithley++
15:03 glusterbot lalatenduM: kkeithley's karma is now 20
15:08 kkeithley yes, when 4.5.3 ships, we'll do `fedpkg update` to push it into the fedora updates-testing and then updates YUM repos. That's independent of pushing different spec files into the git repo.
15:08 kkeithley s/4.5.3/3.5.3/
15:09 kkeithley into the fedora dist-git repo
15:11 lalatenduM kkeithley, I thought , once we commit 3.6 specfile changes we wont be able to do fedpkg build for 3.5.3  and we have to do only scratch builds
15:11 lalatenduM kkeithley, as to do fedpkg build , we need to commit those dist git
15:11 lalatenduM isn't it?
15:11 kkeithley it's a bit harder, but it's not impossible
15:12 kkeithley yes, `fedpkg build` requires committing to dist-git
15:13 kkeithley after we commit a 3.6.0beta1 .spec and do the builds, later on when Neils wants to do the 3.5.3 or 3.5.3 beta builds, he has to revert to the last 3.5 .spec and commit it.
15:14 kkeithley so there's some "churn" as the .spec jumps back and forth between 3.5 and 3.6. I've done it in the past. I'm not going to force you guys to do it now.
15:14 lalatenduM kkeithley, ndevos , not sure which one will be released first 3.4.5 or 3.6.0 GA
15:14 kkeithley Although Humble already committed his
15:14 lalatenduM kkeithley, agree
15:15 lalatenduM s/3.4.5/3.5.3/
15:17 kkeithley right, I figured that's what you meant.
15:19 ndevos lalatenduM: it does not really matter, a fedora release should not see a major update during its lifetime
15:19 ndevos lalatenduM: fedora 21 is in alpha/beta already, so we can only ship 3.6.x for fedora 22
15:20 kkeithley well, I haven't followed that rule very religiously. But maybe it's time to start.
15:21 ndevos yeah, I think we should stick to the fedora guidelines where possible, we're doing stable releases anyway, users should get those rather than a major update
15:21 kkeithley major/minor/teeny = 3.4.5 (or 3.5.2)  We haven't had a _major_ release in a long time.  But I'm perverting the intent.
15:22 ndevos yeah, well :P
15:23 kkeithley ;-)
15:23 ndevos I'll be gone for the day now, ttyt!
15:23 kkeithley If we were still shipping RPMs in epel though, we'd be stuck at 3.2.7, or doing painful backporting.
15:23 kkeithley yeah, ttly
15:24 kkeithley ttyl
15:24 lalatenduM ndevos, ttyl
15:25 lalatenduM ndevos, when you have time, plz send your suggestion to the original mail thread so we can refer it later
15:26 lalatenduM kkeithley, I cant imagine backporting current changes for 3.2.7 ;(
15:26 lalatenduM it would have been so painful
15:26 kkeithley yep
15:31 kkeithley Has there been discussion in the CentOS Storage SIG or in the CentOS SIGs in general, about shipping versions? I don't expect we want to be stuck shipping the same version three years from now that we're shipping today. We'll want a path forward to newer versions.
15:33 lalatenduM kkeithley, yes, we dont have restrictions to put newer versions there
15:34 lalatenduM kkeithley, so dont have to do much of  of back porting  I guess
15:34 kkeithley right
15:35 lalatenduM kkeithley, if we go by updates policy in fedora as ndevos metioned it , we should put 3.6 in F22 , but others should have 3.5.x
15:36 lalatenduM kkeithley, as mentioned in http://fedoraproject.org/wiki/Updates_Policy Humble^
15:38 kkeithley Well, any particular Fedora release has such a short lifespan...  And the number of people using Fedora for production is generally thought to be pretty small; non-existent even. Nobody ever complained. But we should start.
15:39 kkeithley Gluster has matured quite a bit too. There's not as much reason to _push_ people to newer releases now, as there was three years ago.
15:39 hagarth joined #gluster-dev
15:40 kkeithley People who really want, e.g. 3.6.0, once it's released, for fedora20 can get it from our own yum repo on download.gluster.org.
15:41 lalatenduM kkeithley, right
15:42 kkeithley Back to the original topic though, you guys can decide whether you want to incur/endure the churn of 3.5.x/3.6.x .spec files in dist-git. I'll live with whatever you decide.
15:44 kkeithley Maybe it's less painful if the 3.6.x spec is only in the master and f22 branches, and the 3.5.x spec is only in the f21 and f20 branches
15:48 hagarth1 joined #gluster-dev
15:49 lalatenduM kkeithley, yeah I also think so
15:50 lalatenduM kkeithley, then, when we do any changes to f20 or f21 branches , we have to re-base them against each other , not master
15:57 jobewan joined #gluster-dev
15:57 * hchiramm_ reading chatlogs
16:01 hchiramm_ kkeithley++ thanks :)
16:01 glusterbot hchiramm_: kkeithley's karma is now 21
16:02 hchiramm_ kkeithley, lalatenduM I think we have to think about the commit strategy bit in detail and act..
16:03 hchiramm_ however I was thinking if we commit the 3.6spec only to fedora master dist-git and keep other branches uninformed ?
16:03 lalatenduM hchiramm_, I have started all the scratch builds
16:03 hchiramm_ ok .
16:03 hchiramm_ lalatenduM++
16:03 glusterbot hchiramm_: lalatenduM's karma is now 25
16:06 Gaurav_ joined #gluster-dev
16:10 lalatenduM hchiramm_, ttyl leaving now, have sent the mail abt scratch builds
16:12 hchiramm_ lalatenduM, ok..
16:12 hchiramm_ I will try to make it today night, if not will proceed rest on tomo morning
16:26 krishnan_p joined #gluster-dev
16:34 tdasilva joined #gluster-dev
17:10 anoopcs joined #gluster-dev
17:11 anoopcs joined #gluster-dev
19:34 MacWinner joined #gluster-dev

| Channels | #gluster-dev index | Today | | Search | Google Search | Plain-Text | summary