Re: State of 8.2.0, July 12, 2008
On Mon, Jul 14, 2008 at 8:17 AM, Morgan Collett <[EMAIL PROTECTED]> wrote: > On Sun, Jul 13, 2008 at 06:11, Michael Stone <[EMAIL PROTECTED]> wrote: >> Trac additions >> - we want to add a 'review' option to the 'action needed' field. >> - anything else? > > I suggested to Joe for the Trac meeting that we have a 'needs info' > option there, for when the reporter has not provided enough > information and a developer cannot diagnose or reproduce the problem - > e.g. requesting logs from the reporter. Isn't that what the 'communicate' action is for? ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: State of 8.2.0, July 12, 2008
On Sun, Jul 13, 2008 at 06:11, Michael Stone <[EMAIL PROTECTED]> wrote: > Trac additions > - we want to add a 'review' option to the 'action needed' field. > - anything else? I suggested to Joe for the Trac meeting that we have a 'needs info' option there, for when the reporter has not provided enough information and a developer cannot diagnose or reproduce the problem - e.g. requesting logs from the reporter. Regards Morgan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: State of 8.2.0, July 12, 2008
On Sun, Jul 13, 2008 at 8:31 PM, Marco Pesenti Gritti <[EMAIL PROTECTED]> wrote: >> b) Do you agree that it's a good idea to start maintaining both a >> development and a release buildstream now? Would you prefer to wait >> for a few more days? If so, why? > > I'm just back from vacation and I don't have a very good view of the > state of things yet. But my feeling is that we could do it a long as > we are able to get good responsiveness on the "please tag package X" > requests, 1-2 days max. Regardless of *when* we start using the release buildstream, please make sure to announce it on devel and to resync with joyride. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: State of 8.2.0, July 12, 2008
On Sun, Jul 13, 2008 at 6:11 AM, Michael Stone <[EMAIL PROTECTED]> wrote: > Sugar slowness & redraws > - Sugar feels really slow both because it is and because we're seeing lots of >intermediate states (redraws, overlapping icons, ...) I assume you mean this regressed compared to Update.1. Can it be reproduced consistently on a clean joyride installation? Do we have a ticket about it? Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: State of 8.2.0, July 12, 2008
On Sun, Jul 13, 2008 at 6:45 PM, Michael Stone <[EMAIL PROTECTED]> wrote: >> What do you mean with "positive report"? > > The same statement that a tag like 'joyride-2153:+' means: someone > specifically retested an issue on a build known to contain the > package(s) you want to ship and could not reproduce the issue according > to the testcase(s) discussed in the ticket. For many modules you will not have a one to one mapping between a ticket and a package. You will usually have several tickets related to a single package and also multiple packages related to a single ticket. This is just to say that "Dennis will automatically merge changes from joyride into the 8.2 stream as soon as he sees a positive report about the changes" is unlikely to happen. >> Do we need to notify Dennis as soon as we verified the changes are >> working? If so, how? > > a) How would you like to do so? Well, ideally I'd like to do it with bodhi: https://admin.fedoraproject.org/updates If that's not possible we could use trac in a similar way, i.e. open a ticket with a list of nvr to tag (and probably with references to the tickets the package fixes). > b) Do you agree that it's a good idea to start maintaining both a > development and a release buildstream now? Would you prefer to wait > for a few more days? If so, why? I'm just back from vacation and I don't have a very good view of the state of things yet. But my feeling is that we could do it a long as we are able to get good responsiveness on the "please tag package X" requests, 1-2 days max. >> > Joe really needs nice package-level changelogs in order to quickly figure >> > out >> > exactly which individual issues he's supposed to be testing in a given >> > build. >> > I'm sure he'll give us some hints soon about what he wants to see; in the >> > meantime, please put some extra effort into writing informative changelog >> > entries that will be useful for QA (and for me). (I'm looking at you, >> > kernel >> > team!) >> >> For the Sugar packages what we can easily produce is a list of tickets >> that has been fixed (we have a ticket for each change) and testcases >> for these fixes. These can be generated automatically from the git log >> so that we don't put too much overhead on the module maintainers. > > I've seen. Could you post a link to the code which performs this task so > that we can see whether it can be extended to other subsystems? (Also, > does it publish any web-pages or is it email-only?) ReleaseReport class in here: http://dev.laptop.org/git?p=sugar-jhbuild;a=blob;f=scripts/report.py;h=566c7680c049b4005246e06283f49aa7d485dca0;hb=HEAD It just print out the report results at the moment. I'm happy to tweak it to "push" the reports as appropriate as soon as I know in what form the testing team would like to have changelogs/testcases reported. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: State of 8.2.0, July 12, 2008
On Sun, Jul 13, 2008 at 10:22:50AM +0200, Marco Pesenti Gritti wrote: > On Sun, Jul 13, 2008 at 6:11 AM, Michael Stone <[EMAIL PROTECTED]> wrote: > > Dennis recently made us an 8.2 release build stream. For the time being, > > you're > > all doing a great job providing good fixes, so Dennis will automatically > > merge > > changes from joyride into the 8.2 stream as soon as he sees a positive > > report > > about the changes. Please leave us messages in Trac, then poke us if you > > need > > to attract our attention to your change. (In a couple of weeks, we'll start > > being more selective about which changes we include [at which time this > > communication will become more important.) > > What do you mean with "positive report"? The same statement that a tag like 'joyride-2153:+' means: someone specifically retested an issue on a build known to contain the package(s) you want to ship and could not reproduce the issue according to the testcase(s) discussed in the ticket. > Do we need to notify Dennis as soon as we verified the changes are > working? If so, how? a) How would you like to do so? b) Do you agree that it's a good idea to start maintaining both a development and a release buildstream now? Would you prefer to wait for a few more days? If so, why? > > Joe really needs nice package-level changelogs in order to quickly figure > > out > > exactly which individual issues he's supposed to be testing in a given > > build. > > I'm sure he'll give us some hints soon about what he wants to see; in the > > meantime, please put some extra effort into writing informative changelog > > entries that will be useful for QA (and for me). (I'm looking at you, kernel > > team!) > > For the Sugar packages what we can easily produce is a list of tickets > that has been fixed (we have a ticket for each change) and testcases > for these fixes. These can be generated automatically from the git log > so that we don't put too much overhead on the module maintainers. I've seen. Could you post a link to the code which performs this task so that we can see whether it can be extended to other subsystems? (Also, does it publish any web-pages or is it email-only?) Thanks, Michael ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: State of 8.2.0, July 12, 2008
Am 13.07.2008 um 06:11 schrieb Michael Stone: > > http://dev.laptop.org/~bert/8.2-joyride.html > - Bert, could you please make a version of your status pages which > shows > package changelog entries? Thanks in advance! Unfortunately not - at least the last time I tried I found it too complicated to scrape them with my brain-dead script. Where would the entries come from nowadays? Reinier's scripts are far more extensible, he would basically just need to add 8.2: http://dev.laptop.org/~rwh/announcer/joyride_vs_update1.html - Bert - ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: State of 8.2.0, July 12, 2008
On Sun, Jul 13, 2008 at 6:11 AM, Michael Stone <[EMAIL PROTECTED]> wrote: > Dennis recently made us an 8.2 release build stream. For the time being, > you're > all doing a great job providing good fixes, so Dennis will automatically merge > changes from joyride into the 8.2 stream as soon as he sees a positive report > about the changes. Please leave us messages in Trac, then poke us if you need > to attract our attention to your change. (In a couple of weeks, we'll start > being more selective about which changes we include [at which time this > communication will become more important.) What do you mean with "positive report"? Do we need to notify Dennis as soon as we verified the changes are working? If so, how? > Joe really needs nice package-level changelogs in order to quickly figure out > exactly which individual issues he's supposed to be testing in a given build. > I'm sure he'll give us some hints soon about what he wants to see; in the > meantime, please put some extra effort into writing informative changelog > entries that will be useful for QA (and for me). (I'm looking at you, kernel > team!) For the Sugar packages what we can easily produce is a list of tickets that has been fixed (we have a ticket for each change) and testcases for these fixes. These can be generated automatically from the git log so that we don't put too much overhead on the module maintainers. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
State of 8.2.0, July 12, 2008
Dear world, Here's a brief overview of the status of the 8.2.0 release process. (Notes: I apologize in advance that I was not able to make this overview more succinct or better organized. I hope that these issues will resolve themselves as we come to share a greater understanding of the actual state of the release.) Michael === Procedural Notices: Dennis recently made us an 8.2 release build stream. For the time being, you're all doing a great job providing good fixes, so Dennis will automatically merge changes from joyride into the 8.2 stream as soon as he sees a positive report about the changes. Please leave us messages in Trac, then poke us if you need to attract our attention to your change. (In a couple of weeks, we'll start being more selective about which changes we include [at which time this communication will become more important.) Joe really needs nice package-level changelogs in order to quickly figure out exactly which individual issues he's supposed to be testing in a given build. I'm sure he'll give us some hints soon about what he wants to see; in the meantime, please put some extra effort into writing informative changelog entries that will be useful for QA (and for me). (I'm looking at you, kernel team!) === Bugs you should watching or trying to fix: (See the end for the key to the status codes.) 5104, 5527 DBG ??? Reconnecting to encrypted access points with NM \ http://lists.laptop.org/pipermail/devel/2008-July/016335.html 7474 DBG sayamindu Amharic compose key broken 7480 DSN ??? Networking configuration reset button 7458 DBG dsaxena Suspend/Resume (S/R) lockups many TST dilingerTouchpad bugs. \ http://lists.laptop.org/pipermail/devel/2008-May/013580.html 7095 OWN ??? Library bundle installation 7353 DBG dgilmoreF-9 Bloat ???TST ??? OFW refresh 7392 TST martin_xsa DS backup/restore 7384, 7434 TST cjb Power management (PM) control panel entry (CPE). 4951, 7396 TST cscott Activity Updater CPE. 6797 PKG ??? Rainbox/X race === General issues: Keymap retesting: - we need to systematically check all our keymaps; in particular, en_US, am_ET, es_PR, es_UY, pt_BR, ht_HT, and ??? Sugar slowness & redraws - Sugar feels really slow both because it is and because we're seeing lots of intermediate states (redraws, overlapping icons, ...) - what else is going on besides the rainbow/X race? Telepathy-based collaboration: - some change were made to the Telepathy CMs and to the PS. what effect, if any, did they have? - which, if any, collaboration scenarios can be relied on today? - what's the actual state of Gadget? === Random questions: lease delegation: - is the initramfs correctly checking the contents of the leases file for v2 leases? Walter + Peru security: - what did Walter want to tell us? Trac additions - we want to add a 'review' option to the 'action needed' field. - anything else? 7466 DSN ??? tamtam symlinks. \ seems like this should be fixed in TamTam; not pilgrim. 7448 TST cscott updates from 656 to joyride fail. \ ick 7442 DBG ??? weird interactions between X and VTs. \ are these interactions dangerous? === Status Codes Key: ??? - status or author unknown TST - needs to be tested in a build BLD - needs to be put into a build PKG - pkg needs to be built DBG - debugging/diagnosis still needed DSN - design needed STK - stuck; a decision is needed about how to proceed SGN - a signoff is needed ESC - canceled or siginificantly reduced in priority FIN - successfully finished MSG - communication needed ROT - solution has bitrotted OWN - owner needed === Currently useful links http://dev.laptop.org/~bert/8.2-joyride.html - Bert, could you please make a version of your status pages which shows package changelog entries? Thanks in advance! http://dev.laptop.org/report/21 - Fixed-timespan report on changes to 8.2.0 bugs. http://dev.laptop.org/report/20?TIME=40;page=1; - Adjustable-timespan report on changes to 8.2.0 bugs. http://pilgrim.laptop.org/~pilgrim/xo-1/streams/8.2/ - 8.2.0 build stream http://xs-dev.laptop.org/~cscott/xo-1/streams/joyride/ - Joyride build stream === Things that m_stone is falling down on: - making sure that the localization team is happy - containing the enthusiasm of certain 1cc-based developers to include new features like activity-updates and lease delegation - figuring out what the actual release blockers are - keeping up with Gregorio's writings - getting reliable numbe
