Hi there, Sorry for the lack of response, I was swamped at work last week and only going through my email now... ;)
On Thu, Jul 17, 2008 at 1:10 PM, David Chisnall <[EMAIL PROTECTED]> wrote: > On 16 Jul 2008, at 20:33, Quentin Mathé wrote: > >> Hi David, >> >> Le 16 juil. 08 à 19:04, David Chisnall a écrit : >> >>> Hi Everyone, >>> >>> It's time for me to put on my release manager hat again and start the >>> ball rolling for the 0.4 release. I'd like to pencil in the end of >>> September for a tentative release date. >> >> Good idea :-) Sounds very optimistic though. > > Well, release dates have a habit of slipping, so I'd rather pick one > closer to the present. End of September is probably a tad optimistic, but setting a deadline is good. We do have quite a few cool things to show for a 0.4 release, so it's worth trying (if slip to an october release date, it's no big deal either). > >>> For future releases (up until 1.0), we have decided that odd numbered >>> point releases should be 'user' releases and even numbered point >>> releases should be 'developer' releases. This means that the focus >>> for 0.4 will be frameworks, developer tools, example apps, and >>> documentation. >>> >>> Things I definitely want to see in 0.4: >>> >>> - Pragmatic Smalltalk 1.0 >>> - EtoileUI 1.0 >> >> These two can be ready in time I think.The time could be too short for >> real in-depth code review of EtoileUI though. > > That's fine. I'd like to see all of the EUI APIs reviewed before 0.4, > but the code can be reviewed incrementally afterwards. Pragmatic Smalltalk and EtoileUI will be the two corner stones of the 0.4 imho, so we shouldn't attempt to do the release if we are not sure of their status. >>> - CoreObject 1.0 >> >> Not really sure we can make it in time. We can include it as is >> without the persistency layer enabled though. >> I may be able to finish the code that bridges it with EtoileSerialize. >> It would be helpful if you can make EtoileSerialize "rock-solid" and >> helps me to pin down the current crash I get on Ubuntu. haven't yet >> investigated it again because Valgrind doesn't work well on any of my >> systems, so I got to set up a new one. > > EtoileSerialise is solid on FreeBSD. I can't reproduce the crash you > get on Ubuntu, but I'd be happy to help you track it down, especially > if other people are able to reproduce it (call for testers!). > >>> - EtoileFoundation 1.0 >>> - Stable Camaelon release >> >> I wouldn't count on these two. I mean they are going to be part of >> the release but I don't think we have time to improve the code, tune >> the API and write all the doc. > > Most of EtoileFoundation is documented. The big thing I want to do > here is gut the uuid library and just pull the bits we actually use > directly into EtoileFoundation. I'd also like to remove some of the > UK* classes that are not used. > > For Camaelon, does Nicolas have an opinion? What exactly is not stable ?.. (not saying there's nothing to improve, just asking if there are stability issues right now?) > >> This also holds for the IconKit, even if many applications uses it, it >> won't probably be improved, finished and reviewed in time. > > Okay. > >> Cleaning the UnitKit code a bit would be nice and integrating your >> UKMock code too. I haven't taken a look at it yet :-/ > > Sure. UnitKit is in quite a good state now, and the mock object code > can go in easily. The current UKMock code is far from being really complete I think. > >>> - Memory leak in Azalea fixed >> >> Sure. >> I also need to fix session instability issues that can arise with >> System. >> >>> All of these frameworks should have (vaguely) stable APIs, API >>> documentation, and simple developer examples. The timeline I would >>> like to see us stick to is: >>> >>> August 1st: Create 0.4 branch in svn. Code should be copied in here >>> from trunk after reviewing and fixing any show-stopper bugs. >>> >>> September 1st: Feature freeze in 0.4 branch. If it's not a bug fix, >>> it doesn't go in the branch, and no commits are made to the branch >>> without review by at least one member of the core team other than the >>> author. >>> >>> September 30th: Tag 0.4 branch. Official release, everyone has a >>> party, distributions get to have fun packaging it all up. >> >> Honestly I don't think it's doable. If we push it one month back, we >> could succeed (EtoileFoundation and Camaelon put aside). >> I have also planned to take two weeks of vacations during August, so >> this isn't going to help. >> Aside of that, I'm ok with the timeline organization. > > I'll keep this as a tentative timeline, but not be too upset if it > slips (as long as it doesn't slip six months again...) I think it's a good approach -- we have to set a date, and we have to decide what makes the cut or not for the release. September 30th is probably too agressive, and I think an october release is more likely; but we can give it a shot and see how it turns out. >>> I'd really like to see the music player app make it in (either as a >>> user application or as a CoreObject / EtoileUI example), >> >> Sure. Well, only if Eric finds a better name for it ;-) > > Definitely - EtoileTunes is fine as a working title, but we can't use > it for the release. Anyone want to offer some good suggestions? > >> I'll also wrote an extended version of the minimal ObjectManager >> (visible in the last page of my Swansea EtoileUI presentation). I'll >> commit it, once I cleaned it a bit. I'd like to reuse interesting code >> of Outerspace like Freedesktop trash support, but I doubt I'll have >> time to work on that. >> The features are roughly: >> - Browsing CoreObject graphs and file systems with the FS backend >> - Copy/Move/Link/Create/Delete File/Directory operations without UI >> feedback for the progression >> - Multiple ObjectManager window support >> - Several views: Hierarchical List, Browser, Icon (very limited) + all >> the dev tools that can be injected if you enter in Live Development >> mode >> - Path View for the current URL >> - Pick and drop: drag and copy, copy/cut/paste for objects/files (with >> some instability if you try border cases :-) >> - Advanced UI customization (but the customization will be lost once >> the modified window is closed) > > Sounds good. > >>> What other thing should be in >>> this release? User applications are less of a priority - we have >>> until 0.5 to get them really polished - but it would be nice to >>> have a >>> few working, at least as examples. Well, there's the documentation stuff that I need to submit asap, and we should have after that an ok documentation process that we can use. As a dev/framework release, documentation should be one of our main focus. Actually, shouldn't we try to write tutorials (even short) ? This might be worth delaying the release by a month, in fact. >> >> Many other things are going to be in the release as dependencies, but >> they don't have to be specially outlined since they haven't really >> evolved for a while. > > I will probably begin creating a new /stable branch and move in the > core requirements, then pull in things needed to build them. > >> A structured text editor as Nicolas has been working on would be nice, >> a rudimentary photo manager too. I could eventually turn the crude >> MarkupEditor example (for plist and XML) I wrote for EtoileUI into a >> real application if there is an interest. But as we discussed and >> planned it during the hackataton, it makes more sense when combined >> with Nicolas' structured editor. > > All of these sound good. Nicolas, what's the status of the structured > editor? Still uncomplete. I have been extremely busy at work -- theoretically things should settle now though. It would be nice to have it, but right now the more important things would probably be the doc & camaelon than the editor. Such editor or other applications shouldn't anyway be the focus for 0.4 -- more for the upcoming applications push on 0.5, no ? >> Aside of the ObjectManager, we'll probably have a basic or not so >> basic IDE for Smalltalk. That's relatively trivial to do specially if >> we write it in Smalltalk with EtoileUI. I have been working recently >> on some EtoileUI features for increasing the ability to get a Self/ >> Morphic feeling when you use Smalltalk and EtoileUI together. > > Shiny. The only big things remaining with Smalltalk are supporting > upwards funargs (needs promoting bound variables into the block > objects) and block returns (needs me to play with LLVM exception > handling a bit more). > >> Another thing that would be nice and easy to do, is to write the >> missing glue code between Hardware preference application and >> SystemConfig. We got several SystemConfig contributions from Nyap Hong >> Koh for the keyboard related settings. If someone is interested to >> work on that, you can get in touch with me. > > Would, indeed, be shiny. Any volunteers? > > David > _______________________________________________ > Etoile-discuss mailing list > [email protected] > https://mail.gna.org/listinfo/etoile-discuss > -- Nicolas Roard "I love deadlines. I like the whooshing sound they make as they fly by." -- Douglas Adams _______________________________________________ Etoile-discuss mailing list [email protected] https://mail.gna.org/listinfo/etoile-discuss
