upstream-devel Mailing List for Upstream Log Transfer System
Status: Alpha
Brought to you by:
mweerasinghe
You can subscribe to this list here.
2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(4) |
Sep
(11) |
Oct
(29) |
Nov
(27) |
Dec
(18) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
(5) |
Feb
(11) |
Mar
(9) |
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2008 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Jack_Sparrow <hoo...@gm...> - 2008-01-25 13:45:44
|
I am interested in the project and would like whatever information you feel I might be able to use. Jack_Sparrow #Ubuntu |
From: Mahangu W. <ma...@gm...> - 2007-08-24 12:29:22
|
Hello All, Just thought I'd ping the list and see if anyone would be interested in getting Upstream on the road again. My *nix wifi issues seem to be getting sorted out, so I'll be able to commit some time to working on the project again. If you remember, I had to drop out because my connectivity sucked and it became very difficult to commit or even stay in touch. Anyway, my driver issues seem to be getting sorted out, so I was just wondering if anyone would be interested in having a go at this again. Anyway, this convo with Jason pretty much sums it up. <lastnode> wondering if you and ryan would be interested in re-evaluating where we are in the field now, and getting back in to upstream? <lastnode> i know it's been a while <jrib> it's weird, I actually did a checkout of upstream yesterday and was wondering where you were because I hadn't seen you around in so long <lastnode> sweet <lastnode> thing is, i sorta feel outta my depth with the internal classes ryan wrote <lastnode> i dont understand jack to be honest <jrib> haha me too So Ryan, in short, we need you. :) I'm proposing we go easy for a few months, and just make commits as time permits. Jason suggested (and I totally endorse this), that instead of new features, we try and iron out the bugs, and make this as stable as possible. He also said that he's got a package in to gutsy, so packaging python shouldn't be a problem now (this was a major issue the last time around, if you remember). Anyway, let's hear what you guys have to say. Regards, Mahangu |
From: Karl G. <kam...@in...> - 2007-04-28 13:31:50
|
Jason Ribeiro wrote: > Hey everyone, > =20 Hi mate (and all) > How about a meeting next week to discuss what we want to focus on. > I've been pretty busy with school lately but that will be over soon, > so I hope to do some work on upstream next week. What does everyone > thinking about a quick meeting sometime at the end of next week? > =20 Sorry about any inaction on my part. > Unfortunately, we didn't get the latest upstream into feisty, but I'm > sure a backport could be arranged if we get it packaged into gusty. > > How is everyone doing? > =20 About to get busy - Container of stuff left for PNG 3 days ago, which means in the next 2-3 months i have to write a bunch of doco for someone else then go overseas. i'll be around for the near future though. kk > Jason > =20 --=20 Karl Goetz User of gNewSense: Free as in Freedom - http://www.gnewsense.org Australian Ubuntu users team - http://wiki.ubuntu.com/AustralianTeam User of Debian, The Universal Operating System - http://www.debian.org |
From: Jason R. <jas...@gm...> - 2007-04-28 13:24:59
|
Hey everyone, How about a meeting next week to discuss what we want to focus on. I've been pretty busy with school lately but that will be over soon, so I hope to do some work on upstream next week. What does everyone thinking about a quick meeting sometime at the end of next week? Unfortunately, we didn't get the latest upstream into feisty, but I'm sure a backport could be arranged if we get it packaged into gusty. How is everyone doing? Jason |
From: Ryan Z. <zei...@gm...> - 2007-03-20 02:32:18
|
Hey All, So, first off, apologies for the absolutely monstrous e-mail that I seem to= =20 have got going on here, I've just thought up a bunch of things that might b= e=20 fun and exciting for the long term. Just thought I'd bring up several more points about things that may, or may= =20 not be useful for the next version. One thing I've noticed is that througho= ut=20 the trunk, in some places, we use method signatures like=20 obj.this_is_a_method() and in others, namely, mostly in Kayak we end up wit= h=20 functions like obj.thisIsAMethod(). This is largely a stylistic point, but= =20 since we decided to standardize on using tabs for indentation, I feel like = we=20 should probably standardize this as well, along with maybe putting it up on= =20 the Wiki somewhere, so if we do manage to attract another developer the kno= w.=20 My personal feeling is that it should be the obj.thisIsAMethod() and=20 this_is_a_static_method() for methods and free functions respectively. I've= =20 written code the other way, but that sort of seems to make sense to me. Jus= t=20 thought I'd throw that out there. The other thing I wanted to talk about, was our current variety of log=20 modules. First off, every module seems to reimplement basic file/pipe=20 reading. My personal feeling on the matter is, we could easily switch to a= =20 factory pattern where each plugin returns an object for us to use. We could= =20 conveniently write a base file reader class and a command reader class. Thi= s=20 could theoretically make writting a new plugin like 2 lines of code. I don'= t=20 know if this is feasible either, but it might also allow for us to be 1337= =20 hax0rz and use some kind of pluggable backend for file reading, possibly=20 using either KIO or gnome-vfs if it is present. This is, however, a seconda= ry=20 concern, the more interesting things come from a reduction of duplicated=20 code. Theoretically, a log plugin could do whatever it felt like, as long a= s=20 it is extended from some base class that we ourselves implemented abstractl= y=20 which provides some kind of "read" method, but we could also provide=20 implementations of a file reader and a command pipe reader that sit on top = of=20 the previously mentioned abstract base class. This would make all sorts of= =20 things easy. A similar thing could theoretically also be done with submissi= on=20 modules as well. Obviously, this is somewhat more difficult, as it forces u= s=20 to design an abstract base class that can handle all of the various post=20 formats that are adopted by the different pastbins. I do however, think tha= t=20 it could be feasible for us to design an abstract base class that implement= ed=20 some kind of "non-submit" as well as a fully implemented class that can=20 handle the most obvious cases of submitting to a pastebin. T his would work= =20 similarly to log modules. If we do it carefully, and put a great deal of=20 thought into the design, I'm sure we could even implement something that=20 might let us get some kind of status back out of the modules. Similarly, I= =20 know that gnome-vfs and KIO have http and https utilities. We could try and= =20 implement things in such a way that they rely on these if available. Just=20 some ideas, and thoughts to ponder. This could similarly allow us to ensure= =20 that in most of the cases, a submit module or a log module could be written= =20 basically, without almost any knowledge of programming at all. Just copy an= d=20 paste type stuff. The final thing that I wanted to propose was our thoughts for validation. I= =20 know that currently, we do all sorts of validation things. I remember back= =20 when we were designing things, a conscious decision was made, in order to=20 ensure that no modules that didn't appear to be of the correct type can't b= e=20 used. Obviously, if we switch to this new factory method, it will be more=20 difficult to determine what we do ahead of time in the case of a module. I'= d=20 like to propose that validation in the base class be restricted merely to=20 ensuring that a plugin module has the appropriate information that is=20 required to show to the user in the interface, i.e. The name, group, etc. A= ny=20 other problems we simple deal with at runtime with generic catch-all=20 exception clauses. So, I know I've written a sizeable chunk, so, just to go back and review, I= 'd=20 like to propose the following style guide for methods throughout the base static functions: this_is_a_static_function() class methods: obj.thisIsAMethod() Also, reworking of the design of the log plugins and the submit plugins to= =20 provide base classes that can do most of the work, and can be stored in the= =20 base. =46inally, the loosening of validation so that modules that will probably f= ail=20 will be silently dropped at runtime failures, instead of cluttering with to= ns=20 of debug output about whether the correct various methods and fields are=20 present. I.E. just the current fields, and a check to ensure that an=20 instantiation hook is present. So, I know that was a rather massive amount of stuff to throw at you, so,=20 please take your time, ponder, tear down, all sorts of fun stuff. I hope al= l=20 three people who are reading this are doing well ;-). Regards, Ryan |
From: Jason R. <jas...@gm...> - 2007-03-19 00:51:52
|
I'm going to implement the "make sure we get a paste URL" method. I hate gmail's reply to one person on a mailing list "feature"... Jason On 3/18/07, Mahangu Weerasinghe <ma...@gm...> wrote: > Hi Ryan, > > then the submission was successful, which isn't necessarily true. I feel like > > we should contact the pastebin sites that we are actually using and inquire > > as to the define characteristics of a success page and a failure page. From > > Can't we just check out the success and failure pages ourselves and > then grep or search for a specific phrase on each page to decide if > the submission worked? Would another way be to see if a paste URL is > returned? If none is returned we can safely assume that something went > wrong, I think. Anyway yes, this is one area that really need some > exploring. > > Regards, > Mahangu > > -- > I can do everything through him who gives me strength. > - Philippians 4:13 (NIV) > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Upstream-devel mailing list > Ups...@li... > https://lists.sourceforge.net/lists/listinfo/upstream-devel > |
From: Mahangu W. <ma...@gm...> - 2007-03-19 00:41:30
|
Hi Ryan, > then the submission was successful, which isn't necessarily true. I feel like > we should contact the pastebin sites that we are actually using and inquire > as to the define characteristics of a success page and a failure page. From Can't we just check out the success and failure pages ourselves and then grep or search for a specific phrase on each page to decide if the submission worked? Would another way be to see if a paste URL is returned? If none is returned we can safely assume that something went wrong, I think. Anyway yes, this is one area that really need some exploring. Regards, Mahangu -- I can do everything through him who gives me strength. - Philippians 4:13 (NIV) |
From: Ryan Z. <zei...@gm...> - 2007-03-18 18:25:45
|
Hey All, So, I'm going through the pastbin modules, and I noticed that none of the=20 pastebin modules currently seem to actually check that the submission=20 succeeded. They appear to merely assume that if a network error didn't occu= r,=20 then the submission was successful, which isn't necessarily true. I feel li= ke=20 we should contact the pastebin sites that we are actually using and inquire= =20 as to the define characteristics of a success page and a failure page. From= =20 there, we can actually screen scrape to make sure that we got a successful= =20 submission. I feel like if we can't get this information from a pastebin=20 site, or, if when we contact them, they want us to not use them, we should= =20 drop support for that module. This might cause use to lose a few, but I fee= l=20 like, in the end it would be more worthwhile. Ryan |
From: Mahangu W. <ma...@gm...> - 2007-03-16 05:02:59
|
Hello All, I'm pushing for Upstream being included in the Lanka Software Foundation's project list for Google Summer of Code 2007. In order to do this however, I need to list some things that need to be done. If you can think of a feature that would around three months to implement, please let me know asap. Note that you don't need to map out the specifics or approach. Abstract ideas are just fine. Regards, Mahangu -- I can do everything through him who gives me strength. - Philippians 4:13 (NIV) |
From: Jason R. <jas...@gm...> - 2007-03-06 13:37:27
|
that's good for me On 3/6/07, Mahangu Weerasinghe <ma...@gm...> wrote: > Saturday morning is fine. 8am-ish? That's around nine thirty pm Friday > night for you guys, I think? > > On 3/5/07, Jason Ribeiro <jas...@gm...> wrote: > > Thursday evening or later this week would be best for me. > > > > Anytime Saturday is okay with me, what time is best for you on > > Saturdays Mahangu? > > > > Jason > > > > On 3/5/07, Mahangu Weerasinghe <ma...@gm...> wrote: > > > Saturdays and Sundays are better, but pretty much any weekday evening > > > is fine as well. Can someone suggest at time? > > > > > > On 3/5/07, Ryan Zeigler <zei...@gm...> wrote: > > > > Hey All, > > > > I'm of the opinion that we all sort of need some short little meeting just to > > > > synchronize, cuz I haven't seen anyone in forever. I don't have any proposed > > > > times, I just wanted to get the ball rolling. Pretty much anytime next week > > > > would work for me, since I'll be on vacation > > > > Ryan > > > > > > > > ------------------------------------------------------------------------- > > > > Take Surveys. Earn Cash. Influence the Future of IT > > > > Join SourceForge.net's Techsay panel and you'll get the chance to share your > > > > opinions on IT & business topics through brief surveys-and earn cash > > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > > _______________________________________________ > > > > Upstream-devel mailing list > > > > Ups...@li... > > > > https://lists.sourceforge.net/lists/listinfo/upstream-devel > > > > > > > > > > > > > > > > > > > > > -- > > > I can do everything through him who gives me strength. > > > - Philippians 4:13 (NIV) > > > > > > ------------------------------------------------------------------------- > > > Take Surveys. Earn Cash. Influence the Future of IT > > > Join SourceForge.net's Techsay panel and you'll get the chance to share your > > > opinions on IT & business topics through brief surveys-and earn cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > > _______________________________________________ > > > Upstream-devel mailing list > > > Ups...@li... > > > https://lists.sourceforge.net/lists/listinfo/upstream-devel > > > > > > > > -- > I can do everything through him who gives me strength. > - Philippians 4:13 (NIV) > |
From: Ryan Z. <zei...@gm...> - 2007-03-06 03:07:18
|
Hey All, So, one of the things I'm working on in the trunk is switching the plugin=20 loaders from a system where they go to sleep for a short amount of time and= =20 then wake back up again and check if they are really done with a task to on= e=20 that uses events. I also decided to sort of redo the code, since it is very= =20 ugly and hackish in the current incarnation. However, I'm having trouble=20 synchronizing them. To the best of my understanding the code gets trapped i= n=20 a .wait() call when there is nothing left to wait for. Setting a timeout=20 value on the wait() solves this problem, but I feel like thats not the best= =20 way of doing it, since it kind of defeats the purpose of it at all. However= ,=20 my best attempts at using locks seem to have failed. If anyone can help me,= =20 the code is in the PluginLoader class methods __import_wait__(),=20 __validation_wait__(), __ithread_end__(), and __vthread_end__(). If anyone= =20 has any insight to shed on the problem. I'd be appreciative. I aksed in=20 #python and was told that if I'm clearing events at all my code is probably= =20 wrong, but they seemed generally unhelpful and it made me kind of sad. Ryan |
From: Mahangu W. <ma...@gm...> - 2007-03-05 15:46:44
|
Saturdays and Sundays are better, but pretty much any weekday evening is fine as well. Can someone suggest at time? On 3/5/07, Ryan Zeigler <zei...@gm...> wrote: > Hey All, > I'm of the opinion that we all sort of need some short little meeting just to > synchronize, cuz I haven't seen anyone in forever. I don't have any proposed > times, I just wanted to get the ball rolling. Pretty much anytime next week > would work for me, since I'll be on vacation > Ryan > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Upstream-devel mailing list > Ups...@li... > https://lists.sourceforge.net/lists/listinfo/upstream-devel > > > -- I can do everything through him who gives me strength. - Philippians 4:13 (NIV) |
From: Ryan Z. <zei...@gm...> - 2007-03-05 15:32:37
|
Hey All, I'm of the opinion that we all sort of need some short little meeting just = to=20 synchronize, cuz I haven't seen anyone in forever. I don't have any propose= d=20 times, I just wanted to get the ball rolling. Pretty much anytime next week= =20 would work for me, since I'll be on vacation Ryan |
From: Karl G. <kam...@in...> - 2007-02-16 22:51:03
|
Ryan Zeigler wrote: > Hello All, > So, I think I got that bug that was causing modules to not be found, re= verting=20 > fixed it just fine. So, unless something wonky happened I think we are = good=20 > for branch. I was also wondering if ya'll were at all interested in hav= ing a=20 > meeting at say 9 EST on Monday to discuss future plans. It can be earli= er or=20 > later, I just though I'd throw out a time. > Ryan > =20 > =20 Depends, what is EST relative to GMT? kk --=20 Karl Goetz User of gNewSense: Free as in Freedom - http://www.gnewsense.org Australian Ubuntu users team - http://wiki.ubuntu.com/AustralianTeam User of Debian, The Universal Operating System - http://www.debian.org |
From: Ryan Z. <zei...@gm...> - 2007-02-16 21:31:47
|
Hello All, So, I think I got that bug that was causing modules to not be found, revert= ing=20 fixed it just fine. So, unless something wonky happened I think we are good= =20 for branch. I was also wondering if ya'll were at all interested in having = a=20 meeting at say 9 EST on Monday to discuss future plans. It can be earlier o= r=20 later, I just though I'd throw out a time. Ryan |
From: Mahangu W. <ma...@gm...> - 2007-02-15 15:00:48
|
Hi Ryan, Thanks for reporting in. :-) I too have been mad busy, as well as sick, though most of that is over now. I'll be online this weekend, starting tomorrow (Friday) and will try my best to be around on IRC for anything we need done. As for work, I think after we revert to the unbroken revision, we pretty much just need to find a packager and get this REVUd. If at all, a few more log-modules would be cool, but that's about it. Everyone, if there are any bugs that need to be fixed before release, please post to this thread. Regards, Mahangu On 2/14/07, Ryan Zeigler <zei...@gm...> wrote: > So guys, I know there is talk about getting 0.3 out the door this weekend. I > know I've been sort of MIA for a while, but I've almost succeeded in digging > myself out from under my work, so I should be useful from a developer > standpoint this weekend. That being said, what do we need to get done to get > 0.3 out the door. I know there is a problem with the module loader just not > returning any modules, which I think can be solved by reverting a few > revision. But other than that, what is considered necessary? > Ryan > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Upstream-devel mailing list > Ups...@li... > https://lists.sourceforge.net/lists/listinfo/upstream-devel > > > -- I can do everything through him who gives me strength. - Philippians 4:13 (NIV) |
From: Ryan Z. <zei...@gm...> - 2007-02-15 02:39:36
|
So guys, I know there is talk about getting 0.3 out the door this weekend. = I=20 know I've been sort of MIA for a while, but I've almost succeeded in diggin= g=20 myself out from under my work, so I should be useful from a developer=20 standpoint this weekend. That being said, what do we need to get done to ge= t=20 0.3 out the door. I know there is a problem with the module loader just not= =20 returning any modules, which I think can be solved by reverting a few=20 revision. But other than that, what is considered necessary? Ryan |
From: Ryan Z. <zei...@gm...> - 2007-02-12 01:06:09
|
I can attempt to be around from that time. I propse if the bug isn't easily= =20 found we simply revert the module loader, since I haven't made any changes= =20 that do anything to it. I probably stepped on something I shouldn't have by= =20 accident. I guess it serves as a testament to how flakey the current design= =20 really is. *Scratches a note on the TODO list*. I'll try and be around late= r=20 in the week, but college decided to hit me hard and fast this semester so... Ryan |
From: Jason R. <jas...@gm...> - 2007-02-12 00:58:35
|
Hey everyone, UVF for feisty was Feb. 8 so we missed that, but I spoke with some MOTU's about filing a UVF exception to get a newer version of upstream into feisty. They informed me that we should have a package ready before filing. They also said that the fact that the current version in feisty fails to work with the new ubuntu pastebin is a good reason to file a UVF exception. So it seems like the exception would likely be approved. Here's the relevant info on the wiki: https://wiki.ubuntu.com/FreezeExceptionProcess#head-9523bc4076ff011324d67cddc97969ec609618d6 We should sort out the current bug that seems to fail to validate all the modules at random times and then get to packaging. We could always revert to an earlier version if we can't correct this issue in time, but it would be nice to just resolve it. If anyone wants to work on it together I'll probably be around #upstreamdev Monday evening EST. Mahangu, did anyone ever get back to you about packaging? Jason On 2/1/07, Ryan Zeigler <zei...@gm...> wrote: > That seems to work. I was looking back at some of the base classes, and I > realized its a tangled mess, but it works, and with us trying to release > soon, I'm hesitant to break it, so since after 0.3 we are gutting a large > part of the internals anyway, thats worth leaving put. But, ok, sometime this > weekend I might sit down and try and write a fuzzer script or something to > throw at Lodge and see if I can get it to break. Other than that, nice to be > squared away. > Ryan > > On Thursday 01 February 2007 02:08:44 pm Mahangu Weerasinghe wrote: > > Hi Ryan, > > I think we're pretty much ready for 0.3. If at all, the addition of a > > few more log-modules may be beneficial. As far as packaging goes, I > > think Jason is on that, and I'm trying to contact Fujitsu as well. > > Jason has filed a bug report requesting that python-dialog be synced, > > so hopefully this will be done soonish. > > > > Of course, Lodge needs to be tested thoroughly as well. We don't want > > it to break when the packagers get their hands on it. :-) > > > > Stdin support, which was requested by Karl, has already been finished, > > so that's about it from my end. Does anyone else have any suggestions? > > > > Mahangu > > - > > > > On 2/1/07, Ryan Zeigler <zei...@gm...> wrote: > > > Hey All, > > > So, obviously, we've been going for a release date in the not too distant > > > future. I just wanted to send out a ping to everyone and see if there is > > > anything slated for 0.3 that we absolutely feel the need to get done. If > > > not, we can think about branching soon. > > > > > > Ryan > > > > > > ------------------------------------------------------------------------- > > > Using Tomcat but need to do more? Need to support web services, security? > > > Get stuff done quickly with pre-integrated technology to make your job > > > easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache > > > Geronimo > > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > > _______________________________________________ > > > Upstream-devel mailing list > > > Ups...@li... > > > https://lists.sourceforge.net/lists/listinfo/upstream-devel > > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier. > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Upstream-devel mailing list > Ups...@li... > https://lists.sourceforge.net/lists/listinfo/upstream-devel > > > |
From: Jason R. <jas...@gm...> - 2007-02-10 18:37:34
|
On 2/7/07, Karl Goetz <kam...@in...> wrote: > Hi all. > Pending .3, i thought i would update and re promote this doc. > Its layed out like a man page, but is a plaintext file. it could be used > as either a readme, or converted into a proper manpage. > I'm hoping people can provide some feedback, and include/not as required. > > Apart from a general check, I'm hoping people can look at these > specifically: > * The lists of modules > * The examples section The first example: upstream kgoez "A cat keeps eating my mouse" --video --log= might be better if we either specify a log or just not include that switch in the example. > * is the pastebin module=log module? (have i confused something?) No, there are pastebin modules, which usually get called "submit modules" in the code. and there are also log modules. However, log modules are categorized. So the "--video" switch asks for all of the log modules in the category "video". The "--log" switch just lets you choose individual modules without calling everything in a category. For example "--video" grabs xorg.conf and also runs lspci. But if someone just needed to run "lspci", they would instead specify "--log=lspci" without the "--video". I hope that clears up the confusion, or did you mean something else? Thanks Karl, it looks great. Jason |
From: Karl G. <kam...@in...> - 2007-02-07 05:41:41
|
Hi all. Pending .3, i thought i would update and re promote this doc. Its layed out like a man page, but is a plaintext file. it could be used as either a readme, or converted into a proper manpage. I'm hoping people can provide some feedback, and include/not as required. Apart from a general check, I'm hoping people can look at these specifically: * The lists of modules * The examples section * is the pastebin module=log module? (have i confused something?) Thanks, kk. -- Karl Goetz User of gNewSense: Free as in Freedom - http://www.gnewsense.org Australian Ubuntu users team - http://wiki.ubuntu.com/AustralianTeam User of Debian, The Universal Operating System - http://www.debian.org |
From: Ryan Z. <zei...@gm...> - 2007-02-01 20:23:25
|
That seems to work. I was looking back at some of the base classes, and I=20 realized its a tangled mess, but it works, and with us trying to release=20 soon, I'm hesitant to break it, so since after 0.3 we are gutting a large=20 part of the internals anyway, thats worth leaving put. But, ok, sometime th= is=20 weekend I might sit down and try and write a fuzzer script or something to= =20 throw at Lodge and see if I can get it to break. Other than that, nice to b= e=20 squared away. Ryan On Thursday 01 February 2007 02:08:44 pm Mahangu Weerasinghe wrote: > Hi Ryan, > I think we're pretty much ready for 0.3. If at all, the addition of a > few more log-modules may be beneficial. As far as packaging goes, I > think Jason is on that, and I'm trying to contact Fujitsu as well. > Jason has filed a bug report requesting that python-dialog be synced, > so hopefully this will be done soonish. > > Of course, Lodge needs to be tested thoroughly as well. We don't want > it to break when the packagers get their hands on it. :-) > > Stdin support, which was requested by Karl, has already been finished, > so that's about it from my end. Does anyone else have any suggestions? > > Mahangu > - > > On 2/1/07, Ryan Zeigler <zei...@gm...> wrote: > > Hey All, > > So, obviously, we've been going for a release date in the not too dista= nt > > future. I just wanted to send out a ping to everyone and see if there is > > anything slated for 0.3 that we absolutely feel the need to get done. If > > not, we can think about branching soon. > > > > Ryan > > > > -----------------------------------------------------------------------= =2D- > > Using Tomcat but need to do more? Need to support web services, securit= y? > > Get stuff done quickly with pre-integrated technology to make your job > > easier. Download IBM WebSphere Application Server v.1.0.1 based on Apac= he > > Geronimo > > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat= =3D121642 > > _______________________________________________ > > Upstream-devel mailing list > > Ups...@li... > > https://lists.sourceforge.net/lists/listinfo/upstream-devel |
From: Mahangu W. <ma...@gm...> - 2007-02-01 19:08:51
|
Hi Ryan, I think we're pretty much ready for 0.3. If at all, the addition of a few more log-modules may be beneficial. As far as packaging goes, I think Jason is on that, and I'm trying to contact Fujitsu as well. Jason has filed a bug report requesting that python-dialog be synced, so hopefully this will be done soonish. Of course, Lodge needs to be tested thoroughly as well. We don't want it to break when the packagers get their hands on it. :-) Stdin support, which was requested by Karl, has already been finished, so that's about it from my end. Does anyone else have any suggestions? Mahangu - On 2/1/07, Ryan Zeigler <zei...@gm...> wrote: > Hey All, > So, obviously, we've been going for a release date in the not too distant > future. I just wanted to send out a ping to everyone and see if there is > anything slated for 0.3 that we absolutely feel the need to get done. If not, > we can think about branching soon. > > Ryan > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier. > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Upstream-devel mailing list > Ups...@li... > https://lists.sourceforge.net/lists/listinfo/upstream-devel > -- I can do everything through him who gives me strength. - Philippians 4:13 (NIV) |
From: Ryan Z. <zei...@gm...> - 2007-02-01 16:55:24
|
Hey All, So, obviously, we've been going for a release date in the not too distant future. I just wanted to send out a ping to everyone and see if there is anything slated for 0.3 that we absolutely feel the need to get done. If not, we can think about branching soon. Ryan |
From: Karl G. <kam...@in...> - 2007-01-19 13:26:49
|
On Fri, 2007-01-19 at 03:10 -1000, Mahangu Weerasinghe wrote: > Awesome. How about Saturday evening my time (GMT + 5.30). Any time > between three and nine should be fine. Not sure what time that is for > you guys. > > On 1/19/07, Ryan Zeigler <zei...@gm...> wrote: > > Hello everyone, > > So I know that there have been some plans for a meeting that have cropped up > > from time to time, but have never really materialized. I just wanted to throw > > out there that I'm good for a meeting pretty much anytime in the next few > > days except sunday. > > > > Ryan > > i dont get home until sunday night my time, so i wont be able to make it. gl all. kk |