[yast-devel] WebYaST status 12-Apr-2010
jsrain, jdsn, tgoettlicher, mvidner, jsuchome, mkudlvasr, mzugec, jreidinger, kkaempf, schubi, vgorobets vgorobets: worked on forms, validation in time and mail settings, looking for better solutions schubi: bugfixing, registration + patch installation kkaempf: non-WY stuff, bugfixing, will prioritize jreidinger: bzilla, NTP back-end (to test) mzugec:et the "RebootNeeded = true" in patchinfo for this purp submitted users layout, working on password validation unification, some non-WY in the queue mkudlvasr: fixed firewall (possible cutting user's connection), will be finished today jsuchome: mostly non-WY, looking into latest snapshot mvidner: P1 bugfixing tgoettlicher: non-WY stuff, will test next build jdsn: returned from vacation jsrain: will go for vacation AI everyone: think how we can increase our transparency about our progress to others; e.g. a weekly list of fixed bugs? suggestions welcome by end of today AI everyone: provide the information about changes done since appliance toolking 1.0 release by Wednesday in Fate AI everyone: if running out of important bugs, offer your help to others reminder: we are approaching RC3 this week -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Jiri Srain write:
<snip>
AI everyone: think how we can increase our transparency about our progress to others; e.g. a weekly list of fixed bugs? suggestions welcome by end of today
My suggestion: It must be automatic and it must be linked with bugzilla. So I suggest to force write bnc#<number> to commits and post automatic mail each week list of fixed bugs. If we want only released bugs, then I suggest to grep changes file where should be also bnc#<number> mentioned and send mail with these bugs numbers
reminder: we are approaching RC3 this week
Reminder - submit deadline is today evening Josef -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, parts of webyast -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Mon, Apr 12, 2010 at 11:05:17AM +0200, Josef Reidinger wrote:
Jiri Srain write:
AI everyone: think how we can increase our transparency about our progress to others; e.g. a weekly list of fixed bugs? suggestions welcome by end of today
My suggestion: It must be automatic and it must be linked with bugzilla. So I suggest to force write bnc#<number> to commits and post automatic mail each week list of fixed bugs. If we want only released bugs, then I suggest to grep changes file where should be also bnc#<number> mentioned and send mail with these bugs numbers
We already do produce a list of fixed bugs, in the aggregate change logs: http://w3.suse.de/~mvidner/webyast-appliance/ChangeLog-RC2 http://w3.suse.de/~mvidner/webyast-appliance/daily/2010-04-09/ChangeLog Scrum? http://retro.opensuse.org/ ? ( http://retrospectiva.org/ ) -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
mzugec:et the "RebootNeeded = true" in patchinfo for this purp submitted users layout, working on password validation unification, some non-WY in the queue
Only "working on password validation unification, some non-WY in the queue" is true ;-) -- Best Regards, Michal Zugec Software developer --------------------------------------------------------------------- SuSE CR, s.r.o. e-mail: mzugec@suse.cz Lihovarska 1060/12 tel: +420 284 028 960 190 00 Praha 9 fax: +420 296 542 374 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (4)
-
Jiri Srain
-
Josef Reidinger
-
Martin Vidner
-
Michal Zugec