Rainer Meier schrieb: >> Really, someone was talking about any January deadline? If so, you >> sure 2008 was mentioned? ;) > > Yes, we discussed about the January deadline. 1.0 RC7 is quite stable > from my point of view. > > >> Hmm, finger in the air - Rainer, do you think rc7 can be released as >> 1.0, or does it still need some code added here and there? > > As I wrote to some of you (yes, my mailinglist subscription was broken, > hope it works now) I intended to fix Bug 97 (see > <http://bugzilla.wpkg.org/show_bug.cgi?id=97>) and Bug 98 (see > <http://bugzilla.wpkg.org/show_bug.cgi?id=98>) I wanted to wait until I > can analyze this reports. > > Well it turned out that both of them are not really WPKG bugs. One was a > misbehaving user package and the other one simply misconfiguration. > > Finally I don't see any critical bugs left on WPKG 1.0 RC7. As it has > been around for quite a long time already I would recommend to release it. > > I propose to release it as 1.0.0. After release we will only fix > critical bugs in 1.0.x releases. New feature request and trials go to > the already existing 1.1.x Mx branch (I think I have to look for a > versioning system as WPKG does not seem to use an official one). > > So let's release it. What about these two posted by Frank? http://bugzilla.wpkg.org/show_bug.cgi?id=104 - 'Adds an opening quote to "Adding settings node" - Utterly trivial patch' - I have no objections. http://bugzilla.wpkg.org/show_bug.cgi?id=103 - 'Handling absence of config.xml' says: By default, wpkg.js exits silently without any info if the config.xml file isn't found Last time I tried, wpkg.js did work without config.xml - am I misreading anything? -- Tomasz Chmielewski |