From gerv at mozilla.org Mon Jul 3 10:18:42 2017 From: gerv at mozilla.org (Gervase Markham) Date: Mon, 3 Jul 2017 11:18:42 +0100 Subject: Bugzilla Meeting for July is on Wednesday at 9pm UK time Message-ID: The next monthly Bugzilla public meeting will be on Wednesday July 5th, at 9pm UK time (1pm Pacific, 8pm UTC). http://arewemeetingyet.com/London/2017-07-05/21:00/Bugzilla%20Meeting Agenda is here: https://wiki.mozilla.org/Bugzilla:Meetings Feel free to add stuff you want to talk about, and see you then :-) Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mail at simon.green Tue Jul 4 09:00:28 2017 From: mail at simon.green (Simon Green) Date: Tue, 4 Jul 2017 21:00:28 +1200 Subject: Bugzilla Meeting for July is on Wednesday at 9pm UK time In-Reply-To: References: Message-ID: <3ec93978-d5f1-e3d2-2c14-48afa56b0d33@simon.green> On 03/07/17 22:18, Gervase Markham wrote: > The next monthly Bugzilla public meeting will be on Wednesday > July 5th, at 9pm UK time (1pm Pacific, 8pm UTC). > http://arewemeetingyet.com/London/2017-07-05/21:00/Bugzilla%20Meeting The wiki says the meeting is at 9pm GMT, not 8pm as in this e-mail. -- Simon From gerv at mozilla.org Tue Jul 4 17:22:51 2017 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 04 Jul 2017 18:22:51 +0100 Subject: Bugzilla Meeting for July is on Wednesday at 9pm UK time In-Reply-To: <3ec93978-d5f1-e3d2-2c14-48afa56b0d33@simon.green> References: <3ec93978-d5f1-e3d2-2c14-48afa56b0d33@simon.green> Message-ID: <078B564A-B82B-494D-95F2-BC65941F002C@mozilla.org> The wiki may be using "GMT" incorrectly but colloquially as shorthand for UK time. The meeting is at 9 pm UK time, which is 8 pm UTC during the summer. Gerv -------------- next part -------------- An HTML attachment was scrubbed... URL: From thehailstorm28 at yahoo.com Wed Jul 5 22:09:24 2017 From: thehailstorm28 at yahoo.com (DANIEL DELACRUZ) Date: Wed, 5 Jul 2017 18:09:24 -0400 Subject: Bugzilla Meeting for July is on Wednesday at 9pm UK time In-Reply-To: <078B564A-B82B-494D-95F2-BC65941F002C@mozilla.org> References: <3ec93978-d5f1-e3d2-2c14-48afa56b0d33@simon.green> <078B564A-B82B-494D-95F2-BC65941F002C@mozilla.org> Message-ID: <914F7032-94CE-4D37-9361-6A6E9E96A04E@yahoo.com> \' ; DEBOY8 > On Jul 4, 2017, at 1:22 PM, Gervase Markham wrote: > > The wiki may be using "GMT" incorrectly but colloquially as shorthand for UK time. The meeting is at 9 pm UK time, which is 8 pm UTC during the summer. > > Gerv From dylan at mozilla.com Wed Jul 5 22:12:53 2017 From: dylan at mozilla.com (Dylan Hardison) Date: Wed, 5 Jul 2017 15:12:53 -0700 Subject: Re-Starting Bugzilla development Message-ID: <057B2D05-CEA5-4893-A681-B4ADA83817A6@mozilla.com> Hi everyone! tl; dr I want Bugzilla 6 to basically be a portable version of the code as it exists on bugzilla.mozilla.org So we've discussed this at the previous two Bugzilla meetings, and I've chatted with a few people about this in passing, but to make to official I wanted to announce my intention of rebasing the next major release of Bugzilla on the current bugzilla.mozilla.org code. There needs to be some discussion on what this means, and I don't have all that figured out just yet but I do have a general shape of what the end result is: 1. There will be an upgrade path from the current 5.x release to this new "bmo-based" 6.0 release 2. There will be an upgrade path from the master branch to this as well In this context, "upgrade path" means that the schema will migrate successfully. 3. This doesn't automatically mean BMOs extensions will get merged up, but we may ship them disabled. This is particularly the case when there is code that is mysql-specific (although ideally I'd like to fix that) There are a lot of changes I've seen in RedHat's 5.0 beta that I would love to also merge too -- but as those aren't public yet it isn't on my roadmap. The rationale for doing this is simply there is a large amount of work going into BMO -- including multiple UX improvements (from the new enter bug page to Kohei's effort to redesign the general UI (header/footer). There are also changes that have slipped in to Bugzilla that BMO can never support as implemented, among these are the current implementation of user names (there is a different plan for implementing the same functionality in BMO) and the REST API rewrite. From gerv at mozilla.org Fri Jul 7 09:06:53 2017 From: gerv at mozilla.org (Gervase Markham) Date: Fri, 7 Jul 2017 10:06:53 +0100 Subject: Re-Starting Bugzilla development In-Reply-To: References: Message-ID: <6uidndkcuI2z0sLEnZ2dnUU7-QHNnZ2d@mozilla.org> Thank you, Dylan, for announcing this. As co-assistant project lead, I also believe it's the right way to go to give Bugzilla a healthy future. The world has changed; Bugzilla is now most suitable for organizations which have outgrown Github Issues and similar, and in that case the more "enterprise"-y features of BMO are appropriate. Rebasing on the living and developed BMO codebase, and making sure the two stay close in the future, seems like the best way of making sure upstream development does not stagnate. There are clearly a few things to be worked out about how to implement this plan, and how we can get most quickly to a release. I hope we can have a good discussion about how Dylan's goals might be best achieved. One thing we need to do is make a list of changes to trunk which are not in BMO. This is non-trivial as BMO is technically based on 4.4 but has merged a great deal of code from 5.0 and master. We will then need to work out how we intend to deal with each of those changes - merge it, abandon it, rewrite it or whatever, and whether we do this before or after the first release on the new path. We also need to figure out the best source control architecture. It is my view that this plan will succeed and Bugzilla will thrive if it is just as easy for Mozilla devs to work on Bugzilla as it is on BMO. If additional effort is needed to "upstream" stuff, that won't happen, the two will diverge, and we'll end up in the same position again. So we need to get to a position where the Bugzilla master branch is what BMO ships from weekly. Every so often we can cut a release from there and stabilise and ship it. How we get to the position of the BMO codebase being the master branch remains to be worked out. I guess the start is to import BMO into github.com/bugzilla/bugzilla as a branch that BMO ships from. Then we can start merging stuff into it with Dylan's review. Once we have all that is slated for the first release, we can cut a branch off that and ship. At that point, we can probably "overwrite" our current master with the current BMO codebase branch, and work from there. Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From liework06 at gmail.com Mon Jul 10 07:29:59 2017 From: liework06 at gmail.com (Lie work) Date: Mon, 10 Jul 2017 00:29:59 -0700 (PDT) Subject: Vehicle Advertising | Dot2dot | Digital Printing Message-ID: Dot2dot is your FIRST SOURCE FOR VEHICLE WRAPS by using digital printing in Malaysia. We can wrap any type of vehicle from one to your whole fleet: Car, Van, Trailer, Lorry, Boat, Bus, Truck, Cargo Van, or an entire fleet of semi-trailer, we can handle them all! At DTD, we only use top grade materials in digital printing and only do the top level installation possible for vehicle wraps services. We do it all In House from start to finish so you are getting the top level vehicle wraps available that suits your taste and interest. Allow DTD to work with you to create a visually appealing design for your vehicle wraps advertisement that is positively able to grab 100% attention of people throughout MALAYSIA. At the same time, your marketing impact is even further magnified with the implementation of vehicle wrap, utilizing all the vehicles of your fleet. For information, http://www.dot2dot.com.my/vehicle-wraps-2/ _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From marketemail06 at gmail.com Thu Jul 20 10:42:21 2017 From: marketemail06 at gmail.com (market email) Date: Thu, 20 Jul 2017 03:42:21 -0700 (PDT) Subject: Digital Printing | Online Printing Solutions |Dot2dot Message-ID: <7d0c0143-9f8b-43a6-9dd3-0170abe2d331@googlegroups.com> Digital printing is a process of using digital or electronic files from computer or other digital storage devices as a source. Digital printing won?t use press plates or setup bedding in the printing process. With the advancement in the technology and in printing techniques, digital printing has replaced all other printing techniques in markets. Advantages of Digital printing: There are many benefits associated with digital printing. They are as follows ? Provides top quality with lower cost. ? Distortion of images won?t occur. ? Elimination of heavy printing machinery. ? Reduces time and efforts of digital printing process. ? Short run printing capability. ? More number of design graphics in printing than ever before. For more information http://www.dot2dot.com.my/digital-printing/ _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla