Hi, A few comments below. On Mon, 2010-04-05 at 19:40 +0700, Frank wrote: > I think the especially the last point you're making is quite > important. Sure it's always desirable to have new extensions out as > soon as possible, but from how I understand you I think BCE > developers/maintainers should consider carefully: > > * when is a good time to release a new extension? > * is the extension mature enough yet to be included in packaging? > * are all release requirements fulfillled? > ---- What are they? How do I find out? > > Can releases of new extensions be bundled in a good way? since we're > in schedule with banshee releases, that could be difficult, but it > could be motivation to meet release dates for some. As you might have noticed, we now have a "stable-1.6" branch in the gitorious repo. This should be for bug fixes only, so we probably won't add new extensions on that branch. As for master, we've been quite liberal in adding extensions, as having a low barrier to entry is one of the main point of BCE. Especially as it's easy to disable any problematic extension by passing --disable-extensionname to "configure". What we have done and might do again, is have an extension disabled by default in the build. This would send the message "use this extension at you own risks". We should make sure to update the "configure" output and the documentation if that is the case. > I would volunteer to extend the BCE wiki a bit by some best practices, > especially a package release checklist, again lowering the border to > write new Extensions. That'd be great ! > Also, given time and volunteers at least a quick review of extensions > should be done before releasing. I remember my own StreamRecorder > extension spitting out a lot of useless debugging, easy to fix, but I > somehow missed on that and there was no review until someone got > annoyed by it... > > Thanks for doing a great packaging job, anyway, Chow! > > Frank > > 2010/4/5 Chow Loong Jin <hyperair ubuntu com>: > > On Monday 05,April,2010 11:52 AM, Frank wrote: > >> Hi all, > >> > >> can anyone tell me, how long it takes for the packaging of BCE > >> (specifically for Ubuntu)? How is packaging for BCE organized? I > >> noticed there is quite a time difference between the actual release > >> and the packaging. Any help needed anywhere? I would really like to > >> see the software distributed to the average user base which I don't > >> think possible without packaging. > > > > Sorry for taking so long. The reason there's so much time taken between release > > and packaging is that each release so far has added at least one new extension. > > I expect things to calm down after BCE has been around for a while, but every > > time we upload something with a new binary package, it gets stuck in both > > Debian's and Ubuntu's NEW queue. And every time I have to go through the NEW > > queue, I need to put in extra care to avoid the package getting rejected and > > needing another round-trip through me and the NEW queue again. > > > > Examples of NEW issues that I didn't nail down properly during my last upload to > > Ubuntu -- Banshee.Lirc's files do not have copyright statements and I didn't > > document the copyrights properly, NDesk.DBus is bundled in Banshee.Telepathy.... > > > > Well all those are taken care of now, and upload of the new BCE should be soon. > > > > What would *really* help would be to get as many extensions in between one > > release and another, rather than spreading them out over a number of releases. > > > > -- > > Kind regards, > > Chow Loong Jin (GPG: 0x8F02A411) > > Ubuntu Developer > > > > > > _______________________________________________ > > Banshee-devel-list mailing list > > Banshee-devel-list gnome org > > http://mail.gnome.org/mailman/listinfo/banshee-devel-list > > > > > _______________________________________________ > Banshee-devel-list mailing list > Banshee-devel-list gnome org > http://mail.gnome.org/mailman/listinfo/banshee-devel-list -- Bertrand Lorentz <bertrand lorentz gmail com> > http://bl-log.blogspot.com <
Attachment:
signature.asc
Description: This is a digitally signed message part