| Newsgroups |
gmane.comp.cms.xaraya.devel |
| Organization |
Xaraya |
| Message-ID |
<[email protected]> |
[22:02] <random> *---------- MEETING BEGINS ----------*
[22:03] <random> 1. Site rework (update)
[22:03] <random> 2. Release baseline
[22:03] <random> 3. 2.0.0 release docs (update)
[22:03] <random> 4. Infrastructure (update)
[22:03] <random> 5. Aruba roadmap (discussion)
[22:03] <random> 6. Xaraya documentation concept for the future
(discussion)
[22:03] <random> OK to start with No1?
[22:04] <chris> sure
[22:04] <Robert> Okay with me
[22:04] <Tim1980> :|
[22:04] <random> we started this discussion last week
[22:04] <random> but it sort of got deferred
[22:05] <random> we were told Chris was the lead on this. Is that
correct?
[22:05] <chris> that'll be my fault, yes? rl intervened at an
inopportune moment
[22:05] <chris> but yes, that's correct
[22:05] <random> not a question of fault surely
[22:06] <random> but then you'd be the person to give an update :)
[22:06] <chris> no, but I'm to blame for it being deferred :)
[22:06] <Robert> On the plus side we will be starting that this week
(unless something unexpected happens) Hopefully not speaking out of turn
[22:06] * random hands the mike to chris
[22:06] <chris> the plan at this stage is for robert and I to begin work
on re-organising staging this week
[22:07] <chris> that means re-working categories, culling the plethora
of redundant articles and cleaning up privileges and roles
[22:07] <random> there is a staging site out there yes?
[22:07] <chris> yes
[22:07] <random> is it viewable?
[22:08] <chris> you want access?
[22:08] <random> but go on.perhap squestions at the end
[22:08] <chris> it's not publicly viewable
[22:10] <chris> ok, we actually could do with someone going through the
out of date docs on the main site and flagging the ones which need to go
[22:11] <chris> or that need updating/re-writing to take into account
changes that have happened since the were written
[22:11] <Robert> +1 on that. We could also open the staging site open
to everyone once we have the privs, groups, and cats reorg done.
[22:11] <random> I suppose that could be divided up over several ppl
[22:11] <chris> I'd hoped it could yes
[22:14] <random> done?
[22:14] <chris> until I've had chance to go through things with robert
there isn't a great deal more to say at the moment for staging
[22:14] <random> kk
[22:15] <random> so maybe next week we can revisit
[22:15] <random> and perhaps begin reviewing the content?
[22:15] <chris> absolutely
[22:15] <random> cool
[22:15] <random> anything ellse?
[22:16] <Robert> Nothing to add at this time on item number 1
[22:16] <random> anyone have questions or comments?
[22:17] * random moves on
[22:17] <random> 2. Release baseline
[22:17] <random> this topic was suggested by mikespub
[22:17] <random> to whit
[22:17] <StEgo> yeah, can you clarify what is meant by "baseline" in
this instance?
[22:17] <random> "why bother with 2.0.0when we're already halfway to
2.1.0"
[22:18] <random> it's a reasonable question
[22:18] <chris> I had pev ask a similar question this week
[22:18] <random> 2.0.0 had 4 betas and 2 rcs
[22:19] <random> from a development pov it makes little difference
[22:19] <StEgo> so the "why bother" part is in regard to publishing,
then, right?
[22:19] <StEgo> not dev
[22:19] <random> yes, why bother releasing
[22:19] <StEgo> ok
[22:19] <StEgo> lemme float an idea across:
[22:19] <random> the impact
[22:19] <random> if there is one
[22:19] <StEgo> publish directly to 2.1, but at the same time back-post 2.0
[22:19] <random> is on the marketing side
[22:20] <random> I would think
[22:20] <StEgo> so that we at least have a 2.0 listed before 2.1
[22:20] <random> "why did you guys not release 2.0.0 after sucha long
time"
[22:20] <random> yes
[22:20] <random> it's a consideration of sorts perhaps
[22:20] <random> but go ahead chad
[22:20] <chris> I got the impression that's what we were aiming to do?
ie release of 2.0.0 is imminent
[22:20] <StEgo> we can then refer to the 2.0 release as an "internal"
one or similar
[22:21] <StEgo> with regard to why it wasn't published sooner
[22:21] <StEgo> and 2.1 will be listed above it, so that folx don't get
confused
[22:21] <StEgo> i can work out the marketing spin for the 2.0 release
note with the committee
[22:21] <StEgo> if we want to go that route
[22:21] <random> now I'm confused :)
[22:22] <StEgo> lemme restate to clarify:
[22:22] <StEgo> on the homepage, we publish two news stories simultaneously
[22:22] <StEgo> 2.1 and 2.0
[22:23] <chris> hang on though, is 2.1 ready for release?
[22:23] <StEgo> 2.0 says that it's been around but mostly used
internally and that 2.1 is teh new hawtness
[22:23] <StEgo> am implying we hold off the 2.0 publication until 2.1 is
ready
[22:23] <StEgo> in this case
[22:23] <random> 2.1 needs to go through rcs
[22:23] <chris> ok
[22:23] <StEgo> not saying we pub it right now
[22:23] <StEgo> in either casee
[22:23] <random> k
[22:23] <chris> so why not just release 2.0 now and have done with it?
[22:23] <StEgo> granted, we could, for 2.0
[22:24] <StEgo> but since 2.1 is where we want to push folx
[22:24] <chris> that seems less confusing to me than bumping out two in
one go
[22:24] <StEgo> how far off is 2.1 rc1?
[22:24] <StEgo> less confusing to me too, but it has a practical reason
[22:24] <random> it would have to happen immediately
[22:24] <StEgo> but is not ready, is it?
[22:25] <random> because the next major step for 2.1
[22:25] <random> is merging in the requestmapper scenario
[22:25] <random> and the debris and discussion of that
[22:25] <random> will push any further release back
[22:25] <random> on the other hand the major change to 2.1 so far
[22:25] <StEgo> then, yeah, we'll need to pub 2.0 simply because of the
add'l time it will take to get to 2.1
[22:25] <random> is the blocks reqrite
[22:26] <random> and that appears fairly stable
[22:26] <random> no we could put out a 2.1 rc now
[22:26] <random> there is one reason for doing so
[22:26] <random> and that is
[22:26] <StEgo> then, my orig idea would be pretty solid, i think
[22:27] <random> that 2.1.so far has db changes
[22:27] <random> the rule I think is
[22:27] <random> once we have an official release
[22:27] <StEgo> my concern is putting ppl on 2.0 and letting them get
acclimated prior to switching things around to how 2.1 works
[22:27] <random> we need to provide upgrades
[22:28] <random> if 2.1 is the first real release
[22:28] <Tim1980> I thought 2.0.0 had not gone gold because, docs
needed to be made, and the site needed to be made ready for 2.0.0 content?
[22:28] <random> then no need for upgrade
[22:28] <random> tim: correct
[22:28] <random> and that problem remains
[22:28] <random> because if we go 2.1
[22:28] <random> I hive of a rc inthe next few days
[22:29] <StEgo> huh?
[22:29] <random> so that development can continue on the main branhc
[22:29] <Tim1980> Well we have a timeline for the site to be ready (or
sort of anyway a soft date)
[22:29] <StEgo> you'll have a release candidate in the next few days? is
that what you meant?
[22:29] <random> and then the clock starts ticking on 2.1
[22:29] <random> well sure why not?
[22:29] <StEgo> just needed clarification
[22:29] <chris> ok, so the question becomes do we abandon 2.0 entirely,
I can't see the point of releasing at all if the upgrade from it to
2.1.0 is problematic
[22:29] <StEgo> when you say "abandon"...
[22:29] <random> it's not problematic
[22:30] <chris> as in not release
[22:30] <random> the sqls exist
[22:30] <StEgo> ahh
[22:30] <StEgo> what i'm saying is we do a pseudo-release
[22:30] <chris> I don't have a problem with 2.1.0 being the first gold
release
[22:30] <StEgo> published 5 min prior to the 2.1 release
[22:30] <Tim1980> *Confused* Shuts back up
[22:30] <random> it's just another problem that takes time and testin
[22:31] <random> but however you want to spin 2.0 if we go directly
to 2.1
[22:31] <chris> in fact, I think skipping 2.0 as a gold release is a lot
less confusing
[22:31] <Tim1980> Why lable 2.1.0 2.1.0 at all.
[22:31] <random> Tim's point is valid in the sense that
[22:31] <Tim1980> Why not just call it 2.0.0 Gold?
[22:31] <random> if the docs and site are not ready in reasonable time
[22:31] <StEgo> ex: Homepage: News -> 13:45 "Xar 2.1 Gold Released",
13:39 "Xar 2.0 published"
[22:32] <random> then you'll have the problem all over again a bit
down the road
[22:32] <random> make sense?
[22:32] <Tim1980> Though if the problem of the site and docs is an
issue either way doesn't that mean those issues still need to be
addressed before release of any Jamaica code?
[22:32] <random> that's my point
[22:32] <StEgo> then we could switch "1) site rework" to being "redo
site in 2.1"
[22:33] <StEgo> no?
[22:33] <random> don't see the connection
[22:33] <chris> we can't do that, the site relies on too many 1x modules
which don't have a 2x equivalent
[22:33] <random> btw you might check that
[22:34] <random> I've loaded all the current modules on the demo site
[22:34] <Tim1980> Maybe there needs to be a staff meeting to hammer
out the details of docs, getting the site ready for 2.0.0 content, and
anything else about releases.
[22:34] <Tim1980> Maybe with a full availble and active PMC things can
get "done" instead of talked about :-P
[22:35] <random> there is one more issue in this topic
[22:35] <random> mike talks about legacy blocks or something
[22:35] <random> what he means is
[22:36] <random> putting back in the code for 1x type blocks
[22:36] <random> I had a look
[22:36] <chris> yes, I saw that
[22:36] <random> afaics there are 6 blocks unconverted
[22:36] <random> among the current jamaica modules
[22:36] <chris> sounds about right
[22:36] <random> xarpages, categories, articles, headlines iirc
[22:36] <random> I would suggest that is not a lot
[22:37] <random> and could be converted
[22:37] <chris> I have headlines cats and articles converted locally
[22:37] <chris> so consider those done
[22:37] <random> prior to a 2.1 release oneway or the other
[22:37] <random> aha
[22:37] <random> push dear boy
[22:37] <StEgo> werd up chris!
[22:37] <StEgo> that just leaves xarpages?
[22:37] <chris> I'll push them later :)
[22:37] <random> one block there iirc
[22:38] <random> sowe have laid out the issue I think
[22:38] <random> do we want to think about it?
[22:38] <chris> we have for me, I don't particularly want to return to
the legacy way
[22:39] <StEgo> +1
[22:39] <random> yea I don't think that's necessary
[22:39] <random> of course there are other blocks out there
[22:39] <random> in unconverted modules
[22:39] <StEgo> yeah
[22:39] <random> but they need to be ...uh..converted
[22:39] <StEgo> if we can get a list?
[22:39] <StEgo> even tho they are 3rd party or whatev
[22:40] <StEgo> would make a nice "get your feet wet" for new devs
[22:40] <random> no but the point being the module has to be
converted anyway
[22:40] <StEgo> and we can, of course, work on them as well
[22:40] <random> so the block is just part of the module conversion
[22:40] <chris> agree
[22:41] <chris> no different than re-working templates and function calls
[22:41] <random> yea
[22:41] <random> but when I said do we want to think about it
[22:41] <random> I meant the issue of 2.0 or 2.1
[22:42] <chris> aha, well for me, I think it might be less confusing to
relabel 2.1 as 2.0
[22:42] <StEgo> My vote is on 2.1, with the caveat that we at least
publish something about 2.0 immediately prior
[22:42] <StEgo> ok, there's that too
[22:42] <StEgo> is not a huge issue to just relabel it 2.0?
[22:42] <random> well it's a tad confusing
[22:42] <random> monotone will say one thing
[22:42] <StEgo> ah
[22:43] <random> and the releases another
[22:43] <StEgo> then i say keep it 2.1
[22:43] <random> but apart that
[22:43] <random> no big deal
[22:43] <StEgo> if we publish 2.0 then 2.1 immediately after it will
also look like we are really busy! :-D
[22:43] <Robert> If there is an upgrade path from 2.0.0 to 2.1.0 we
should do a soft release of 2.0.0 soon (once we have at least some
documentation together) then release 2.1.0 with the new site, docs, and
anything else that goes with the release (marketing ect)
[22:44] <random> that's a possibility
[22:44] <Robert> (New site means once the staging site goes live and
is ready, which I would hope be well before 2.1.0 goes final)
[22:44] <StEgo> that works as well, if we keep it REALLY soft
[22:44] <chris> I'm for what robert just said if we're going to release
2.0, I'd like it out of the way and not hitting at the same time as 2.1
[22:44] <StEgo> gotta be soft soft soft tho
[22:45] <StEgo> just a bulleted release note and no fanfare
[22:45] <StEgo> we go full tilt for 2.1
[22:45] <random> you have the release note draft :)
[22:45] <chris> +1
[22:45] <random> +1
[22:45] <StEgo> +1
[22:45] <Robert> +1
[22:45] <Tim1980> +1 too because its a good middle ground
[22:46] <random> cool
[22:46] <random> move on?
[22:46] <StEgo> yup
[22:46] <Robert> yes
[22:46] <chris> sure
[22:46] <random> 3. 2.0.0 release docs (update)
[22:46] <random> leads right into this
[22:46] <random> I sent you all a draft of them
[22:46] <StEgo> yup, got it up
[22:46] <random> cc'd mikespub
[22:47] <StEgo> i'll tackle that rewrite today now that i have the bones
for it
[22:47] <random> cause he did a lot of stuff and might want to set
some accents
[22:47] <StEgo> spent most of the last week packing my house into
storage, so today is the first i've had time
[22:47] <random> rewrite?
[22:47] <StEgo> well
[22:47] <StEgo> dress it up
[22:47] <StEgo> something
[22:47] <StEgo> says "draft" on it
[22:48] <StEgo> could just pub as-is
[22:48] <StEgo> O.o
[22:48] <StEgo> any objections to publishing the 2.0.0 release statement
that marc wrote verbatim?
[22:48] <random> no sure,go ahead
[22:48] <chris> If we're going for a soft release, and no fan fare, it
should be adequate as-is no?
[22:48] <StEgo> yeah, good point
[22:49] <StEgo> hell, i might need to dumb it down a bit
[22:49] <StEgo> ;-)
[22:49] <StEgo> j/k
[22:49] <random> perhaps tim would like to have a look at it, seeing
as he's a marketing guy
[22:49] <random> as I said
[22:49] <random> it isdevoid of marketing speak
[22:49] <StEgo> that's how we want it
[22:49] <chris> good idea
[22:49] <StEgo> we DO want Tim on the 2.1.0 release tho
[22:50] <StEgo> thots?
[22:50] <random> agree
[22:50] <Tim1980> Would be happy to help just email me anything you
want looked at.
[22:50] <random> addy?
[22:50] <Robert> [email protected]
[22:50] <chris> ok, then I'd propose using what marc drafted for 2.0,
and that we begin work on the 2.1 notes as soon as possible so we have
them nailed for that release
[22:51] <random> sent
[22:51] <--| primus has left #pmc (Leaving...)
[22:52] <Tim1980> No idea how the name came about is what Google
suggested when I was invited to gmail so long ago. And thank you will
look at it as soon as I cam.
[22:52] <random> just pls canvas mike on the release notes in case he
has input
[22:52] <Tim1980> Thanks Robert for being faster at me with my email addt
[22:52] <random> so from where I sit there could be a release next
weekend?
[22:53] <chris> sounds reasonable
[22:53] <Robert> What Chris said
[22:54] <random> move on?
[22:54] <chris> yep
[22:54] <random> 4. Infrastructure (update)
[22:54] * random hands the mike to chris
[22:55] * chris pauses for thought
[22:56] <random> you can say "no update"
[22:56] <chris> I can, but I'd sooner find out what was expected
[22:56] <random> Ijust included it cause it was on the agenda last
time unfimished
[22:57] <random> it was stated you were the person infomred
[22:57] <Robert> I would say no update at this time.
[22:57] <random> about the discussions re hosting
[22:57] <random> k
[22:57] <random> move on then?
[22:57] <chris> aha, re hosting, yes, no update at this time would be right
[22:58] <random> it was stated last itme that this is not an urgent
urgent issue
[22:58] <random> but now that presumably dracos isno longer talking
to those OS guys
[22:59] <random> what is to happen?
[22:59] <StEgo> he was talking to them?
[22:59] <random> mailing at least
[22:59] * StEgo thinks the term "alienating" still seems more appropriate
[22:59] <chris> well, the OSU discussion was undertaken by the pmc as a
whole, not just marty
[22:59] <random> kk
[22:59] <random> my mistake
[22:59] <chris> marty took lead as he had more knowledge than the rest
of us, but the initial approach was made by me
[22:59] <StEgo> Chris, is this something you can pick up and roll with now?
[23:00] <chris> sure, I believe robert has been looking into it too,
we'll get together on that this week
[23:00] <random> cool
[23:00] <Robert> We are also looking at other avenues incase OSU
never pans out, but there is nothing to report at this time.
[23:00] <StEgo> how heft a server would we need?
[23:00] <Robert> lol I was trying that before others got there stuff
out :P
[23:02] <random> chad: no idea
[23:02] <StEgo> I'll hit up Neosurge to see if there is still interest
in helping us out
[23:02] <StEgo> if worse comes to worse, i have a dedi that is
perpetually underutilized
[23:03] -->| Bob (TimWilliam-QnJHXE7Cko6b3lgBspJoX+pVTWNl90mP5NbjCUgZEJk@public.gmane.org) has joined
#pmc
[23:03] =-= Bob is now known as godboko71
[23:03] <random> sounds like there are opitons
[23:03] <random> move on?
[23:04] <chris> sure, we'll revisit infrasructure next week
[23:05] <random> strange
[23:05] <random> k
[23:05] <random> 5. Aruba roadmap (discussion)
[23:05] <random> where is Aruba going from here?
[23:05] <random> I put this as a discussion
[23:05] <StEgo> just docs
[23:05] <StEgo> imo
[23:06] <random> cause there is no imminent pressure to take a
decision imho
[23:06] <chris> we scheduled a 1.2.1 release, which, IMO, still needs to
happen
[23:06] <StEgo> much of the Aruba docs could easily apply to Jamaica
[23:06] |<-- Tim1980 has left irc.xaraya.com (Ping timeout)
[23:06] <random> don't see that really
[23:06] <StEgo> really?
[23:06] <random> anything visualy won't work
[23:06] <chris> me neither
[23:06] <StEgo> ahhh
[23:06] <StEgo> ok
[23:06] <random> diffenent theme
[23:06] -->| Bob (TimWilliam-QnJHXE7Cko6b3lgBspJoX+pVTWNl90mP5NbjCUgZEJk@public.gmane.org) has joined
#pmc
[23:06] <godboko71> *Amazed "Robert" hasn't ping timed out*
[23:06] |<-- godboko71 has left irc.xaraya.com (Quit: Miranda IM!
Smaller, Faster, Easier. http://miranda-im.org)
[23:07] <StEgo> from the tone of today's dialog, it sounds like we are
agreed in a general push for 2.1 with renewed energy
[23:07] <chris> +1
[23:07] <random> sounds good :)
[23:08] <random> probably once a hard rlease is imminent
[23:08] <StEgo> we still offer support resources (forem et al) but stop
focus on it from this point forward, the only exception being non-core
mod dev etc.
[23:08] <random> there should be some sort of a decision about aruba
[23:08] =-= Bob is now known as Robert
[23:08] <random> that's one option
[23:09] <random> perhaps pragmatic
[23:09] <random> decision is largely for users
[23:09] <random> so they understand their options for the future
[23:09] <random> how far off is 1.2.1?
[23:10] <chris> 1.2.1 is a bugfix for 1.2.0
[23:10] <chris> no additional functionality to speak of, so it's good to
go (imo)
[23:10] <random> so a couple of weeks then?
[23:10] <chris> yes, I'd say so
[23:11] <random> do we have the resources to release it?
[23:11] <chris> that's a good question
[23:11] <StEgo> any resources you can think of we might not have?
[23:11] <random> cause iirc marty did a lot of the work
[23:11] * StEgo has some gold pieces, lots of mined crystal and a few
trees worth of lumber
[23:11] <chris> the build system was all marty
[23:11] <random> in the previous releases
[23:12] <StEgo> build system?
[23:12] <StEgo> what all was involved in that, anyway?
[23:12] <random> you need the build system
[23:12] <random> if you release base and full
[23:12] <StEgo> well, yeah, but that doesn't explain what it is/does
[23:12] <random> it builds a release
[23:12] <random> tars it and such
[23:13] <random> adds all the necessary files
[23:13] |<-- Robert has left irc.xaraya.com (Ping timeout)
[23:13] <StEgo> there was a system for that other than just tar'ing all
the files together?
[23:13] <random> ignores things such as template cache contents etc
[23:13] <StEgo> ahhh
[23:13] <random> yea
[23:13] <StEgo> did he make it or was he just using it?
[23:13] <random> it's been around for a long time
[23:13] <random> it's inthe install
[23:13] <random> iirc
[23:13] <random> or used to be
[23:13] <random> you run it from command line
[23:14] <StEgo> can we have a monotone qualified individual check on
that pls?
[23:14] <random> actually I may be wrong about it being in the install
[23:14] <StEgo> fwiw, my mtn box went into storage last week
[23:14] <chris> as with other stuff it's light on usage docs as far as
the project is concerned
[23:15] -->| Bob (~Miranda-QnJHXE7Cko6b3lgBspJoX+pVTWNl90mP5NbjCUgZEJk@public.gmane.org) has joined #pmc
[23:15] <StEgo> we can wing it
[23:15] <StEgo> not like the build system did a perfect job anyway
[23:15] <chris> it's not monotone chad, I think it's done using phing
[23:15] <StEgo> at least, not how it was used
[23:15] <StEgo> phing?
[23:16] <chris> yeah, think so
[23:16] <random> ok, I don't see it
[23:16] <random> yeait's phing
[23:16] <random> there used to be a build dir in the install
[23:16] <StEgo> i'd like to see a build that has the directories with
the correct perms and a default config file to use with the correct name
[23:17] <Bob> Can't we just release core and release any modules
inivdully with bug fixes since 1.2.0 . No need for base and Full for a
maintaince release
[23:17] <random> that's the question
[23:17] <StEgo> phing is AN option, not THE option, so we can pub this
release just zipping it up locallly if need be
[23:17] <random> last time marty raised the idea of doing that as of 2.0
[23:17] <chris> I'd go along with that, trouble is, anyone d/loading
1.2.0 full/base will get a buggy core
[23:18] <random> ah
[23:18] <StEgo> how so? and phing would not do that?
[23:18] <Bob> Stop distributing full and base from 1.2.0 :|
[23:18] <StEgo> +1, full is too bloated
[23:19] <Bob> People can use nightlies for getting modules if they
want (not ideal but works until some better build system is in place for
modules in the future)
[23:19] <StEgo> i say we have "module suites" that we could package
together separately, but just release the core on it's own
[23:19] <StEgo> "full" then just becomes a module pack
[23:19] <chris> I think we'd all like module suites tbh
[23:19] <StEgo> and requires core
[23:19] <random> ah there it is
[23:20] <random> com.xaraya.build.dracos
[23:20] <StEgo> werd
[23:20] <chris> thanks
[23:20] <random> I've not used it
[23:20] <random> but might be anoption to explore
[23:20] <StEgo> new toy
[23:20] <chris> none of us have, bus factor of 1
[23:21] <StEgo> good thing we're not idiots. we'll figure it out.
[23:21] <chris> you taking that on?
[23:22] <StEgo> if i had my monotone box still, i'd consider it
[23:23] <random> you sold it?
[23:23] <StEgo> nah, is in storage, along with 95% of everything else i own
[23:23] <StEgo> ;-)
[23:23] <random> ?
[23:23] =-= StEgo is now known as St_Kerouac
[23:23] <random> ic
[23:23] <random> on the road are you
[23:23] <St_Kerouac> ;-)
[23:23] <St_Kerouac> like Jules Winfield, man!
[23:23] <random> with kool aid?
[23:24] <St_Kerouac> lol
[23:24] <St_Kerouac> i think i've had my share of kool aid by now
[23:24] <St_Kerouac> and yours, for that matter
[23:24] <random> lol
[23:25] <Bob> Anyway if base and full are big deals I would still like
to see the core update out when its ready either way
[23:26] <chris> ok, let's get 2.0.0 out next weekend and slate 1.2.1 for
the following weekend
[23:26] <St_Kerouac> +1
[23:26] <Bob> +1
[23:27] <random> kk
[23:27] <random> build is 600k zipped
[23:27] <random> you want it chad?
[23:27] <St_Kerouac> shoot it over
[23:27] <chris> cc me in please :)
[23:28] <random> phing stuff is actually very cool
[23:29] <St_Kerouac> O.o
[23:29] <random> I have a module in dev that should do the same thing
[23:29] <random> but it got a bit stalled
[23:29] <random> email sent
[23:29] <random> anything else here?
[23:30] <Bob> I don't have anything worthwhile to add
[23:30] <chris> as far as the aruba roadmap goes, I don't see any
releases beyond 1.2.1
[23:31] <random> guess you can cross that bridge once the release is
there
[23:31] <chris> I think that needs discussion amongst ourselves, not
necessarily right now though
[23:31] <chris> yes
[23:31] <St_Kerouac> yeah, 1.2.1 will likely be the end of 1x
[23:31] <random> but chad's idea made sense
[23:31] <random> to keep up support at least
[23:31] <random> for some time
[23:32] <chris> oh, yes, for sure
[23:32] <Bob> Yep
[23:33] <random> anything more?
[23:33] <chris> nothing from me
[23:33] <St_Kerouac> docs
[23:33] <St_Kerouac>
http://groups.google.com/group/xaraya/web/xaraya-manual
[23:33] <St_Kerouac> for 2x i guess now
[23:33] <random> I propose deferring the last topic to next week, as
we already have a lot on our plates
[23:33] <Bob> +1 to what Random said
[23:34] <St_Kerouac> kk
[23:34] <St_Kerouac> +1
[23:34] <chris> +1
[23:35] <random> thanks chad
[23:35] <random> we'll get back to it promise
[23:35] <St_Kerouac> no rush
[23:35] <random> any other comments/questions?
[23:35] <St_Kerouac> trust me, i have a big plate already
[23:35] <random> topics?
[23:36] <Bob> Nothing from me this week.
[23:36] <random> going
[23:36] <St_Kerouac> meeting next week at what time/
[23:36] <St_Kerouac> ?
[23:36] <chris> nope, I'm all out of topics too
[23:37] <chris> 20:00 or 21:00 ?
[23:37] <St_Kerouac> 20:00
[23:37] <chris> f'real?
[23:37] <random> is this time OK?
[23:37] <St_Kerouac> or 21?
[23:37] <chris> fine by me
[23:37] <St_Kerouac> 20
[23:37] <random> 20
[23:37] <Bob> +1
[23:37] <St_Kerouac> +1
[23:37] <chris> +1
[23:37] <random> k
[23:37] <random> going
[23:38] <chris> kk
[23:38] <chris> thanks marc
[23:38] <random> you misunderstand
[23:38] <chris> nothing new
[23:38] <random> going
[23:38] <random> gone
[23:38] <random> *---------- MEETING ENDS ----------*