From gerv at mozilla.org Mon Jan 2 16:20:22 2012 From: gerv at mozilla.org (Gervase Markham) Date: Mon, 02 Jan 2012 16:20:22 +0000 Subject: http://bzr.mozilla.org/bugzilla/extensions/ <-- commit policy? In-Reply-To: References: Message-ID: On 29/12/11 08:43, Olav Vitters wrote: > Hello, > > What is the policy to commit to > http://bzr.mozilla.org/bugzilla/extensions/ ? > > I haven't used my commit rights in ages, but could I: > - add some new extension > - commit some terrible code > > or does everything have to go via reviews, even if I add my own > extension(s)? There is no requirement for review for ones own extensions, so if one has commit rights and general permission to commit there, one can just go ahead. However, I'm not entirely sure what the policy is about who has such rights. > Related question: > - which bzr command should I use to add a new extension under > http://bzr.mozilla.org/bugzilla/extensions/ ? I have to look this up every time! I _think_ you just create a new working copy, add the files, check them in, and then bzr push to the appropriate URL. But it would be good to have this written up. Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From lpsolit at gmail.com Mon Jan 9 23:05:47 2012 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Tue, 10 Jan 2012 00:05:47 +0100 Subject: The release after Bugzilla 4.2 will be 4.4, not 5.0 Message-ID: <4F0B72CB.5020109@gmail.com> Hello all, Based on the very slow progress made about the "make Bugzilla pretty" project, the next major release after Bugzilla 4.2 will be 4.4, not 5.0. So the release process for the very near future will be like this: Dec 28, 2011: we released Bugzilla 4.2rc1 (as well as 4.0.3, etc...). January 2012: we are currently working on a relatively small list of blockers for 4.2 final, and which are pretty easy to fix. Once they are fixed, we will release Bugzilla 4.2 final (or maybe 4.2rc2 just before it, if we think that's helpful). We are not in a hurry for the release, as we want to give enough time to people to test 4.2rc1 now that the vacations are over. So this means that the release of 4.2 final should happen early February, I think. This will also mean that Bugzilla 3.4 will be officially unsupported (no more security releases for this branch). April 2012: two months after the release of 4.2 final, we reach the freeze date for new enhancements for the next major release, Bugzilla 4.4! All bugs which were marked as FIXED with their target milestone set to "Bugzilla 5.0" have their target milestone renamed to "Bugzilla 4.4". This means they will all be in Bugzilla 4.4; no worries about that. :) Once we freeze, we will release our first development snapshot for the 4.4 branch, i.e. Bugzilla 4.3.1. April - end of summer(?) We stabilize the branch so that we can release Bugzilla 4.4rc1 as soon as possible. Meanwhile, development goes on on the trunk and new enhancements can still be committed there. After 4.4 is out, the version of the next major release will depend on progress made for some key features. It will be named either 4.6 or 5.0. The exact version doesn't really matter for now as it has no impact on what can be committed into the source code. I hope everything is clear! :) LpSolit From nagalenoj at gmail.com Wed Jan 11 09:15:39 2012 From: nagalenoj at gmail.com (Nagalenoj H.) Date: Wed, 11 Jan 2012 14:45:39 +0530 Subject: Extension to update a flag when resolution/status changed Message-ID: Dear Friends, I've done a simple extension which updates a flag when resolution or bug_status is changed to X. I've attached the extension with this mail. Sending this to list, as someone who needs it in future can get from archives. I've checked this with version 4.0.2. Thanks. -- Nagalenoj H. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: FlagUpdate.pm Type: application/x-perl Size: 2737 bytes Desc: not available URL: From dkl at mozilla.com Thu Jan 12 21:38:16 2012 From: dkl at mozilla.com (David Lawrence) Date: Thu, 12 Jan 2012 16:38:16 -0500 Subject: Splinter extension In-Reply-To: <20111229014553.3fc843d3@angelo.pretender.us> References: <20111229092059.GC28466@bkor.dhs.org> <20111229014553.3fc843d3@angelo.pretender.us> Message-ID: <4F0F52C8.1040607@mozilla.com> On 12/29/2011 04:45 AM, Reed Loden wrote: > On Thu, 29 Dec 2011 10:20:59 +0100 > Olav Vitters wrote: > >> Splinter is available at two locations: >> - http://fishsoup.net/software/splinter/ (original) >> - http://bzr.mozilla.org/bugzilla/extensions/splinter/4.0/files >> (ported to use some different javascript stuff) > http://bzr.mozilla.org/bmo/4.0/files/head:/extensions/Splinter/ is > really the current up-to-date place for the code that runs on bmo. Sorry for the delay. I have just synced bzr.mozilla.org/bugzilla/extensions/splinter/4.0 with what is live on BMO. I also added a 4.2 directory with our latest code that is updated to work with 4.2 (some minor changes). >> I'm looking for a version which is fully self-contained extension (no >> modifications to Bugzilla other than adding the extension). It *must* >> work with attachment_base as well as Bugzilla 4.2. This required some >> patches with the fishsoup one on Bugzilla 3.4 (don't want that!). > From my understanding, the bmo version is completely self-contained, > though dkl would know better. Yes. The original version used ajax calls to get data from Bugzilla but this loads the data directly using Bugzilla core code so should be slightly faster. It did not require any changes to the core Bugzilla code for 4.0 or 4.2. >> Note that I also appreciate if it should support attachments.status >> (custom field used within GNOME). > Pretty sure that got ripped out in bmo's version, but it shouldn't be > too difficult to add back, I bet. Most of the attachment.status is just commented out in the JS code. It may or may not have been completely ported to YUI which I would need to check. BMO does not use attachment statuses and that is a gnome.org customization. Once someone uncommented the relevant JS code and converted it if necessary it should work with the Bugzilla instance if it uses attachment statuses. Unfortunately I do not have the spare cycles to maintain the custom version of our port. dkl -- David Lawrence dkl at mozilla.com From mkanat at bugzilla.org Sat Jan 14 06:22:14 2012 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Fri, 13 Jan 2012 22:22:14 -0800 Subject: Splinter extension In-Reply-To: <4F0F52C8.1040607@mozilla.com> References: <20111229092059.GC28466@bkor.dhs.org> <20111229014553.3fc843d3@angelo.pretender.us> <4F0F52C8.1040607@mozilla.com> Message-ID: <4F111F16.1020408@bugzilla.org> As a side note to this conversation, I think that Splinter has proven useful enough that we should integrate it as a replacement for our current patch-review system. -Max From sbodomerle at gmail.com Sat Jan 14 12:47:46 2012 From: sbodomerle at gmail.com (Sandor Bodo-Merle) Date: Sat, 14 Jan 2012 13:47:46 +0100 Subject: Splinter extension In-Reply-To: <4F0F52C8.1040607@mozilla.com> References: <20111229092059.GC28466@bkor.dhs.org> <20111229014553.3fc843d3@angelo.pretender.us> <4F0F52C8.1040607@mozilla.com> Message-ID: On Thu, Jan 12, 2012 at 10:38 PM, David Lawrence wrote: > On 12/29/2011 04:45 AM, Reed Loden wrote: > >> On Thu, 29 Dec 2011 10:20:59 +0100 >> Olav Vitters wrote: >> >> Splinter is available at two locations: >>> - http://fishsoup.net/software/**splinter/(original) >>> - http://bzr.mozilla.org/**bugzilla/extensions/splinter/**4.0/files >>> (ported to use some different javascript stuff) >>> >> http://bzr.mozilla.org/bmo/4.**0/files/head:/extensions/**Splinter/is >> really the current up-to-date place for the code that runs on bmo. >> > > Sorry for the delay. I have just synced bzr.mozilla.org/bugzilla/** > extensions/splinter/4.0 > with what is live on BMO. I also added a 4.2 directory with our latest > code that is updated > to work with 4.2 (some minor changes). > > Can this live BMO version used on a "plain" bugzilla 4.0.x ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From dkl at mozilla.com Sat Jan 14 14:31:15 2012 From: dkl at mozilla.com (David Lawrence) Date: Sat, 14 Jan 2012 09:31:15 -0500 Subject: Splinter extension In-Reply-To: References: <20111229092059.GC28466@bkor.dhs.org> <20111229014553.3fc843d3@angelo.pretender.us> <4F0F52C8.1040607@mozilla.com> Message-ID: <4F1191B3.1000400@mozilla.com> On 01/14/2012 07:47 AM, Sandor Bodo-Merle wrote: > On Thu, Jan 12, 2012 at 10:38 PM, David Lawrence > wrote: > > > Sorry for the delay. I have just synced > bzr.mozilla.org/bugzilla/extensions/splinter/4.0 > > with what is live on BMO. I also added a 4.2 directory with our > latest code that is updated > to work with 4.2 (some minor changes). > > > Can this live BMO version used on a "plain" bugzilla 4.0.x ? Yes. It *should* work without issue. Let me know if you encounter any problems and I can make the needed adjustments. dkl -- David Lawrence dkl at mozilla.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From sbodomerle at gmail.com Sat Jan 14 16:35:10 2012 From: sbodomerle at gmail.com (Sandor Bodo-Merle) Date: Sat, 14 Jan 2012 17:35:10 +0100 Subject: Expires header for favicon.ico? Message-ID: According to bzr, favicon.ico was never changed since was added to the repo. Even the image is small in size it might be a good idea to make it cache-able... -------------- next part -------------- An HTML attachment was scrubbed... URL: From sbodomerle at gmail.com Mon Jan 16 11:11:55 2012 From: sbodomerle at gmail.com (Sandor Bodo-Merle) Date: Mon, 16 Jan 2012 12:11:55 +0100 Subject: Splinter extension In-Reply-To: <4F1191B3.1000400@mozilla.com> References: <20111229092059.GC28466@bkor.dhs.org> <20111229014553.3fc843d3@angelo.pretender.us> <4F0F52C8.1040607@mozilla.com> <4F1191B3.1000400@mozilla.com> Message-ID: On Sat, Jan 14, 2012 at 3:31 PM, David Lawrence wrote: > On 01/14/2012 07:47 AM, Sandor Bodo-Merle wrote: > > Can this live BMO version used on a "plain" bugzilla 4.0.x ? > > > Yes. It *should* work without issue. Let me know if you encounter any > problems > and I can make the needed adjustments. > > After upgrade to revision 2 with stock bugzilla 4.0.3 i got an empty review page, and the error log say that the file " skins/custom/bug_groups.css" does not exist. Is this CSS BMO live specific? s. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dkl at mozilla.com Tue Jan 17 18:09:58 2012 From: dkl at mozilla.com (David Lawrence) Date: Tue, 17 Jan 2012 13:09:58 -0500 Subject: Splinter extension In-Reply-To: References: <20111229092059.GC28466@bkor.dhs.org> <20111229014553.3fc843d3@angelo.pretender.us> <4F0F52C8.1040607@mozilla.com> <4F1191B3.1000400@mozilla.com> Message-ID: <4F15B976.2060909@mozilla.com> On 01/16/2012 06:11 AM, Sandor Bodo-Merle wrote: > > > On Sat, Jan 14, 2012 at 3:31 PM, David Lawrence > wrote: > > On 01/14/2012 07:47 AM, Sandor Bodo-Merle wrote: >> Can this live BMO version used on a "plain" bugzilla 4.0.x ? > > Yes. It *should* work without issue. Let me know if you encounter > any problems > and I can make the needed adjustments. > > > After upgrade to revision 2 with stock bugzilla 4.0.3 i got an empty > review page, > and the error log say that the file " skins/custom/bug_groups.css" > does not exist. > Is this CSS BMO live specific? > > s. Yes. Anything with /custom/ in the path will likely be a BMO specific change. You can try removing "skins/custom/bug_groups.css" from the style_urls variable in extensions/Splinter/template/en/default/pages/splinter.html.tmpl and see if that clears it up. Are there any other errors in the javascript error log itself as I don't think the missing CSS stylesheet would have caused a completely blank page. A blank page usually means the javascript is not working as the whole Splinter review page is javascript generated. dkl -- David Lawrence dkl at mozilla.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From justdave at bugzilla.org Tue Jan 31 23:51:54 2012 From: justdave at bugzilla.org (David Miller) Date: Tue, 31 Jan 2012 18:51:54 -0500 Subject: New Bugzilla Release Manager Message-ID: <4F287E9A.6020107@bugzilla.org> Some of you may have noticed that Max Kanat-Alexander (mkanat) hasn't been around as much as he used to be lately. He'll be continuing to stay involved with the project, but he's been wearing a lot of hats in the Bugzilla project, and it's hard to keep up with so many of them. Fortunately, Dave Lawrence (dkl) has stepped up to take on the Release Manager role for Bugzilla. Dave's been helping with it for the last couple releases, and been doing awesome, and today's release is the first one he's actually doing in an official capacity. Max will be continuing in his role as Assistant Project Lead, Reviewer, Approver, and the half dozen or so other hats he's been wearing. -- Dave Miller http://www.justdave.net/ System Administrator, Mozilla Corporation http://www.mozilla.com/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/