Log of the #blacklight channel on chat.freenode.net

Using timezone: GMT-05:00
* g8tor leaves00:08
* erikhatcher joins06:27
just e-mailed, but i'll mention here:06:28
in case you haven't seen mention of the meetup in the Bay area tomorrow night: http://wiki.apache.org/lucene-java/LuceneAtApacheConUs2009
* bess joins08:49
* bess_coffee leaves09:09
* bess joins09:18
* bess leaves09:39
* jaron_1 joins09:50
* jaron_1 leaves
* bess joins10:01
* tachyonwill_ joins10:03
* BillDueber joins10:11
* erikhatcher leaves10:12
* erikhatcher joins10:57
* blacklight-git joins11:02
blacklight: 3Matt Mitchell 07master0 SHA1-c51f1a4
changed jetty/test data source from rubyforge to github
http://bit.ly/2NKc6K
* blacklight-git leaves
* erikhatcher leaves11:08
* blacklight-git joins11:12
blacklight: 3Matt Mitchell 07master0 SHA1-76b8a71
changed blacklight plugin url from blacklight-plugin to blacklight
http://bit.ly/2Eoz8j
* blacklight-git leaves
* blacklight-git joins11:19
* blacklight-git leaves
* blacklight-git joins11:22
blacklight: 3Matt Mitchell 07master0 SHA1-624e697
updated for 2.4 tag
http://bit.ly/wwwdd
* blacklight-git leaves
* mbklein_weekend leaves11:29
* blacklight-git joins11:51
blacklight: 3Matt Mitchell 07release-2.40 SHA1-825009c
manually running git commands -- Rails plugin helper will not install branch, Rails Git.clone seems broken for branches.
http://bit.ly/2ZAzt8
* blacklight-git leaves11:52
* ndushay leaves12:06
* bess leaves12:19
* g8tor joins12:23
tachyonwill_: how is it going
I got the commit messages from matt12:24
<tachyonwill_>I'm testing it to make sure it works
* bess joins12:25
<g8tor>hey bess
* ndushay joins
<bess>hey, g8tor12:26
<g8tor>saw the messages from MM
<bess>yeah!
I love the alert setup!
* mmitchell joins12:27
<bess>hey, mmitchell
<g8tor>mmitchell: Hey
<mmitchell>hey!
<bess>g8tor and tachyonwill_ let's see what Matt thinks still needs to happen before we release
<g8tor>mmitchell: how can I heklp fix the issue
<mmitchell>ok, so preparing the 2.4 release
so, here's what i'm doing now... create a branch, "release-2.4"12:28
<g8tor>hay did anyone see the message obn irc? just checking if that worked
<mmitchell>now, make changes to install instructions -- test -- create tag
make sense so far?
<g8tor>yep
<bess>g8tor: yes, the irc messaging worked. I was in here and saw it.
<mmitchell>cool
<g8tor>AWESOME!12:29
<mmitchell>so now, do we want to tag the jetty and data repos too?
i think so actually
<bess>yeah, I think we should
<mmitchell>ok
<bess>b/c we know the 2.4 release works w/ those versions
and they might change, right?
<mmitchell>exactly
<g8tor>i think so as well
<mmitchell>so, that's what i'm doing now
<g8tor>mmitchell: you freak RULE!12:30
oops freaking RULE that is
<mmitchell>this whole thing should be automated. maybe after i complete it all, i'll compile my notes and create a script
<bess>yeah, mmitchell++ :)
<mmitchell>g8tor: ahh shucks :)
<g8tor>lol
<bess>mmitchell: you could also ask Will to do that. Just trying to take stuff off your plate, I know you're busy.
<g8tor>BTW the twitter update worked as well
<mmitchell>bess: cool, sounds great12:31
<g8tor>bess you might want to add the twitter url to the irc channel
you know like the pastie url i see on some other rooms12:32
brb12:33
bess me like the work you did on http://projectblacklight.org/ nice and clean. 12:38
<bess>g8tor: thanks!
<g8tor>mmitchell: is there anything you need from me?12:41
<ndushay>release workers++12:42
mmitchell++ (script for new releases)
<mmitchell>g8tor: no i'm good! almost there :)12:43
<g8tor>cool
does this mean after mmitchell tags the 2.4 release that the move to git is official and can come off the JIRA list?12:44
<tachyonwill_>I tested the template.rb in the branch12:48
I had to make some changes for it to work
* blacklight-git joins12:50
blacklight: 3Matt Mitchell 07release-2.40 SHA1-07e3da0
added git_export helper; implemented git_export and set branch/tag values
http://bit.ly/2N4jdn
* blacklight-git leaves
<g8tor>tachyonwill_: on the master branch?
or the 2.4 release?12:51
<tachyonwill_>2.4
the master branch template worked fine for me
<g8tor>ok me too on the master
what did you have to change for the 2.4 release?
<tachyonwill_>let me first see if mmitchell's changes he just committed make it work12:52
* g8tor says man the irc service hook is freaking awesome
* blacklight-git joins
blacklight: 3Matt Mitchell 07master0 SHA1-f247406
added git_export helper; implemented git_export and set branch/tag values
http://bit.ly/ALdoD
* blacklight-git leaves
<mmitchell>oh yeah, still working on this :)
wow, updates from github here? that's sweet.12:53
i'll try not to use any cuss words in my comments then
<tachyonwill_>okay that change made the git part work
<mmitchell>tachyonwill_: good deal.12:54
<g8tor>mmitchell: on the blacklight-commiters list and on twitter @ http://twitter.com/projblacklight
<mmitchell>i made tags for each of the repos as well, called "release-2.4"
<tachyonwill_>however if you have to go through the rake gems:install part, rake will crash
<mmitchell>g8tor: awesome.
tachyonwill_: hmm, working for me. what kinds of errors?12:55
<g8tor>clear
oops
LOL
<tachyonwill_>it seems to be related to the path in which rake is looking for the rcov.opts
since rcov.opts is in vendor/plugin/blacklight/spec and it is looking in top level spec(which doesn't exist)12:56
<g8tor>bess: will you add the twitter url to the projectblacklight.org as well?
* g8tor GEEKS @ work == BL Goodness!12:57
<tachyonwill_>the hackish way I got around it was to mod template.rb to make a spec folder and copy rcov.opts into it
then everything worked
<mmitchell>tachyonwill_: ok cool. let me have a look here.
* bess leaves13:06
* blacklight-git joins13:09
blacklight: 3Matt Mitchell 07master0 SHA1-5b031aa
made path to rails_root relative using variable, "blacklight_plugin_dir"
http://bit.ly/1HPUxH
blacklight: 3Matt Mitchell 07master0 SHA1-cd9abae
made path to rails_root relative by using variable, "blacklight_plugin_dir"
http://bit.ly/4h2Hnl
* blacklight-git leaves
* tachyonwill_ leaves13:10
* bess joins13:15
* blacklight-git joins13:17
blacklight: 3Matt Mitchell 07release-2.40 SHA1-7ec3b8f
fixed release version
http://bit.ly/3ZPAKN
* blacklight-git leaves
<mmitchell>-- i'll give the scoop on how to do releases in a bit here...
<g8tor>cool
* bess leaves
<g8tor>out to luch (no literally) bb!
* bess joins
* blacklight-git joins13:20
blacklight: 3Matt Mitchell 07release-2.40 SHA1-d5a2536
fixed bug in git_export helper
http://bit.ly/477kLt
* blacklight-git leaves
* blacklight-git joins13:21
* blacklight-git leaves
* blacklight-git joins13:23
* blacklight-git leaves
* blacklight-git joins13:25
blacklight: 3Matt Mitchell 07master0 SHA1-4433326
fixed bug; tag and branch incorrectly set
http://bit.ly/4cMZQz
* blacklight-git leaves
* blacklight-git joins13:27
blacklight: 3Matt Mitchell 07master0 SHA1-d96e73e
Fixed typo!
http://bit.ly/3LZP1r
* blacklight-git leaves
* pmurray joins13:28
* pmurray leaves13:29
* BillDueber leaves13:33
* BillDueber joins13:43
* blacklight-git joins13:44
blacklight: 3Matt Mitchell 07release-2.40 SHA1-576a329
fixed typo
http://bit.ly/32cst5
* blacklight-git leaves
* blacklight-git joins13:51
* blacklight-git leaves
* blacklight-git joins13:52
* blacklight-git leaves
<mmitchell>ok, the branch and tag are called "release-2.4"13:53
here is the tag url: http://github.com/projectblacklight/blacklight/tree/release-2.4
* blacklight-git joins13:54
blacklight: 3Matt Mitchell 07master0 SHA1-273bfc1
another damn typo!
http://bit.ly/MU0MQ
* blacklight-git leaves
* blacklight-git joins13:56
blacklight: 3Matt Mitchell 07release-2.40 SHA1-640b96b
another typo fix
http://bit.ly/2tZvb0
* blacklight-git leaves
* blacklight-git joins
* blacklight-git leaves
* blacklight-git joins13:58
* blacklight-git leaves
* blacklight-git joins
* blacklight-git leaves
* blacklight-git joins14:01
* blacklight-git leaves
* blacklight-git joins14:04
* blacklight-git leaves
<ndushay>ok, the downside to the commits showing up in here is that everything scrolls off my screen.14:08
* bess leaves14:09
<jamieorc>i am not liking this blacklight-git bot. Most of my screen is filled with messages that it has joined and left the room...14:10
* mmitchell_ joins14:11
<g8tor>jamieorc: if people don't like it, it is a simple fix. We thought it would be good for those ppl who have an irc open pretty regularly. Whatever the community wants is fine with me14:13
<jamieorc>g8tor: i think it's a nice idea, but it seems to have connectivity problems14:14
<g8tor>personally I think it blows right now because mmitchell is working pretty hard right now on the release, but do we really expect this level of activity daily? 14:15
I can live with or without it. We do have the blacklight-commiters list and the twitter page so, that should be enough. what say you BL?14:16
* bess joins
<mmitchell_>rats, gotta go to a meeting now. could you all checkout the release-2.4 branch and tag, and try running the template installer? i'll get back and finish asap.14:20
<bess>yes, thank you matt!14:21
* mmitchell leaves14:22
<jamieorc>g8tor: committers mail list is enough for me14:31
<ndushay>g8tor: mail is good for me too.14:34
<g8tor>awwww you guys the Geek in me loves this but I guess its just you and bess that like the irc updates14:37
so is the consensus to remove this service hook? so far 2 - 1 to remove it14:38
<jamieorc>it's just too much noise
<bess>g8tor: yeah, remove the irc service hook14:39
but keep the email one and the twitter one
since those are opt-in
<g8tor>no problemo folks
<bess>g8tor++14:40
<g8tor>ok people I disabled the irc service hook14:42
<bess>thanks, g8tor14:44
so Matt thinks' we're ready to release
can anyone take a look and try a fresh install?
<g8tor>np :-(
<bess>g8tor: was that np (no problem) or "no"?14:45
<g8tor>bess: no problemo
<bess>great
<g8tor>I'll try the fresh install when I finish this thing for my boss
<bess>g8tor: awesome, thank yo14:46
you
<g8tor>no problem I would like to see this move to git put to bed14:47
so I can brag to my boss LOL
<bess>:)14:48
<g8tor>let me be clear people not that I did but that WE did it 14:49
* mmitchell leaves15:06
* mmitchell joins15:10
ok, any reports?15:17
<bess>mmitchell: not yet15:19
<mmitchell>ok. i'd like to run the whole thing again through the rake task i created, if that's ok with everyone
<bess>mmitchell: I say go for it15:20
<mmitchell>cool
jamieorc: is it possible to create a tag in a remote repo, without having a local clone?15:40
<jamieorc>mmitchell: dunno15:41
<mmitchell>jamieorc: ok np
<jamieorc>i doubt it
but i am no expert
<mmitchell>jamieorc: yeah you can't do it.16:02
<jamieorc>not surprised
it's all about working locally and pushing to remote16:03
<mmitchell>jamieorc: exactly. that question came from the old svn within :)
does it make sense to name the release branches the same name as the tags?
<jamieorc>tags and branches shouldn't be the same16:04
<mmitchell>interesting, yeah running into some interesting problem with that.
<jamieorc>you might have a 2.4 branch and a 2.4.1 release, for example
look at how rails does it
<mmitchell>jamieorc: so, here's the thing... we create a branch, make a small change and then release it as a tag, right?
jamieorc: seem like a logical workflow?16:05
<jamieorc>no
tags are different in Git than SVN
<mmitchell>jamieorc: well, i found that out too. a tag is like a "frozen" repo right?
<jamieorc>afaik a tag is a marker in the repo, not a copy like svn
so it probably marks the GUID16:06
every commit has a GUID
<mmitchell>ahh i see
<jamieorc>unlike SVN
so, rails has branches like 2-3-stable16:07
and tags like v2.3.1 and v2.3.2
dunno why they have the v
<mmitchell>jamieorc: ok i see. so the workflow then, to create a branch (stable), and from there tag the different versions for "releases"?16:09
<jamieorc>right
again, I'm not expert or experienced in this
<mmitchell>jamieorc: cool. no that was a huge help. all making sense now. it's just my old svn background kicks in and screws it all up16:10
<jamieorc>but it's definitely a different way of doing things than SVN where "tags" and "branches" are just conventions
<mmitchell>jamieorc: right
<jamieorc>svn just has these virtual copies, and the sections we call "branches" and "tags" could be named anything. But Git has the concept of branches and tags built-in, so they are more rigid in definition16:11
<g8tor>been away for a miute folks I see a vigorus debate going on about tags vs branches16:46
<jamieorc>not VS, just getting understanding16:47
<g8tor>don't mean to be late on this but... afaik tags are simply a moment in time, so no matter what happens later you can always get back to that particular point16:48
<jamieorc>they're different beasts in Git, whereas in SVN, their just different names for the same thing
right, conceptually, I think we have that down
a branch can be modified, a tag is a snapshot not to be changed
<g8tor>now branches are where you can go off into the wild blue yonder without actually affetcting the current line of development i.e. experiments 16:49
so when we release i.e. 2.4 it should be a tag since development is ongoing ?
<jamieorc>well, in terms of the master git repo, branches would be where we put major trees of the code
no16:50
2.4.1 would be the tag
<g8tor>jamieorc: major branches like?
<jamieorc>or are we not using the 3 number system like everyone else in the ruby world?
2 < major .4 < minor .1 < incremental (or something like that)16:51
<g8tor>seems logical
<jamieorc>i can't think of a ruby gem that doesn't use this system... not that this is a gem16:52
but it's the same system
if you bump the major number, it implies broken compatibility with previous versions16:53
* g8tor leaves17:09
* bess leaves17:15
* jamieorc leaves17:18
* mmitchell leaves
* bess joins17:58
* bess leaves18:06
* g8tor joins18:36
* ndushay leaves19:46
* ndushay joins20:12
* ndushay leaves21:22
* mmitchell joins21:56
* mmitchell leaves23:02

Generated by Sualtam