Re: Announcing Project Bugzilla Harmony
Dave Miller <[email protected]> Wed, 03 Jan 2018 16:39:30 -0500
| Newsgroups | gmane.comp.bug-tracking.bugzilla.devel |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --------------070007090402000006090305 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit This got forwarded to me, I don't see that it ever made it to the mailing list, not sure where it ended up. But need to get these replies out there. * From: *Dylan Hardison <[email protected] <mailto:[email protected]>> *Subject: **Re: Announcing Project Bugzilla Harmony* *Date: *December 1, 2017 at 10:50:29 EST *To: *[email protected] <mailto:[email protected]> > > On Dec 1, 2017, at 08:20, Gervase Markham <[email protected] > <mailto:[email protected]>> wrote: > > Hi Dylan, > > Thanks for this - it's good to see some progress on defining what we are > going to be doing :-) > > On 30/11/17 20:36, Dylan Hardison wrote: >> 1. Significant changes to BMO must *not* be required. >> 1.1. No requiring perl 5.14, though nothing prevents us from working >> *better* on modern perls. > > What are the current Perl requirements for stable, trunk and BMO? > > What is the objection to updating the version of Perl we require? > We declare a min version in our code, and this declaration changes the syntax to some degree. For instance, in trunk we have use 5.14.0, which also enables strict mode too (so use strict is not needed). BMO is targeting 5.10.1. It also runs under 5.16 quite well, because 5.16 is used by version-control-tools, and it also runs under 5.24 and 5.26 just fine. But we can't rely on features from those until BMO production is migrated. In about six months I suspect BMO will be running on alpine linux and perl 5.26. I very much want to use only the supported (by the perl community) versions of perl, which is just "the last two versions", but the reality is that I can't upgrade overnight. So for harmony, I'd like to have the minimum version be 5.10.1. I plan on porting https://github.com/mozilla-bteam/bmo-systems <https://github.com/mozilla-bteam/bmo-systems> to upstream bugzilla as well, and >> 1.2. The usernames != login patch has to be backed out (someone >> started this, and I've asked gerv to review it on GitHub) > > Remind us all why this needs to happen? > > Have we shipped this code to anyone? People running the master branch are definitely using it. The problems are a few: it's possible for the DB to be out of sync with the parameter, and if you're registering users when out of sync "strange" things could happen. For BMO the plan is to merely lax the requirement on the login_name field, after adding (multiple) email addresses to the account. This is similar to what many other platforms do. https://bugzilla.mozilla.org/show_bug.cgi?id=1372631 <https://bugzilla.mozilla.org/show_bug.cgi?id=1372631> > >> 2. We are going to follow https://rfc.zeromq.org/spec:42/C4/ >> <https://rfc.zeromq.org/spec:42/C4/> with the understanding that >> "Platform issue tracker" refers to bugzilla.mozilla.org >> <http://bugzilla.mozilla.org> > > What is your goal here? What about our current development model is > broken and needs fixing? Are there specific bits of this rather long > document which you are particularly concerned we adopt? > >> 3. All this work will happen to the "harmony" branch, and we'll >> continue to not touch 'master' to not break anyone that happens to be >> using it. > > I assume "harmony" will be a branch in > http://github.com/bugzilla/bugzilla? > <http://github.com/bugzilla/bugzilla?> > > Will "harmony" start from master, stable, or from the BMO codebase? > > I was rather expecting to start with the BMO code and work back towards > Bugzilla compatibility, rather than starting with master and working > towards BMO compatibility. The former certainly seems like it would be > easier to do... > >> We are not in the business of packaging, there are too many >> combinations to worry about all of them. >> People are welcome to help with packaging Bugzilla 6 / Harmony on >> anything, and nothing drastic will change >> there. But as for releasable products, there are two channels that we >> must support: >> >> 1. A runnable docker container, based on Alpine linux > > I have no particular objection, but why Alpine Linux? What is that? A very small linux distro and the de-facto base image used by high-quality docker containers. > >> 2. A checkout from a tagged commit from GitHub. >> >> The release process for Bugzilla Harmony will amount to tagging a >> commit (from the Harmony branch, more on that later). > > By "release process", do you mean "the process which result in the thing > we call e.g. Bugzilla 6.0"? Or are you talking about some testable > milestones we might ship along the way? > Only the former. I'm going for continuous releases. I'm never going to have time for the other release process. >> The release notes should be exactly the commit messages. Part of >> reviewing a PR is making sure the commit messages tell the >> appropriate story. > > I don't think this particular point is going to fly. It means you can't > really tell any story which spans multiple commits, and it means you > won't be picking out particular features as worth promoting. Doing > things this way will just result in pretty useless release notes. I > understand and agree with your desire to reduce the work involved in > shipping a release, but I think this is an over-economy. You can ignore a subset of commits -- I use this to build the announcements for BMO for the last 4 years. I also think with a continuous release process it is less interesting. We can say "pushing built images is not a release", but these non-releases are the only thing I'm committed to doing or supporting. > >> Commits / Reviews / Pull Requests: >> >> Read the C4 document, that is what contributing to Bugzilla's harmony >> branch should be like. > > That is a somewhat intimidating statement; see my question above. We > have been discussing a significant change to _what_ we are building; a > significant change to _how_ we are building it is somewhat of a bolt > from the blue. I would very much appreciate it if you were to explain > all this a bit more. > The existing process has not worked, it's burdensome. The C4 process is effective for a variety of successful projects. That document gives clear expectations for a lot of situations and encourages patches to actually land. I think that's something important. >> 4. Revert the REST API in favor of the (older) system that BMO is >> still using. > > Why is that necessary? Cannot a new, improved API and the old one live > in parallel? > (explained upthread) >> 5. Ensure a database created by 4.2, 5.0, or the master branch can be >> "upgraded" to from the harmony branch. > > I think you mean the other way around :-) yeah. > >> 10. Port GitHubAuth (this has already been done!) > > Surely the harmony branch needs eventually to support all BMO's > extensions? > Absolutely! The reason harmony is starting from 5.0 is that the other major stake-holder is running (or will be shortly) 5.0 (RedHat). I hope they open up their fork's repo, and I will continue to hope for that. I'm already going to be asking them if they can back-out on multiple bug aliases. Handling the conflicts between BMO and 5.0 is a burden I am able to bear, so I won't ask my RedHat friends to shoulder it. --------------070007090402000006090305 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit <html><head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head><body bgcolor="#FFFFFF" text="#000000"> <div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px">This got forwarded to me, I don't see that it ever made it to the mailing list, not sure where it ended up. But need to get these replies out there.<br> <span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif;color:rgba(0,0,0,1.0)"><b><br> From: </b></span><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif">Dylan Hardison <<a href="mailto:[email protected]" target="_blank">[email protected]</a>><br></span></div> <div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif;color:rgba(0,0,0,1.0)"><b>Subject: </b></span><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif"><b>Re: Announcing Project Bugzilla Harmony</b><br></span></div> <div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif;color:rgba(0,0,0,1.0)"><b>Date: </b></span><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif">December 1, 2017 at 10:50:29 EST<br></span></div> <div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif;color:rgba(0,0,0,1.0)"><b>To: </b></span><span style="font-family:-webkit-system-font,Helvetica Neue,Helvetica,sans-serif"><a href="mailto:[email protected]" target="_blank">[email protected]</a><br></span></div> <br> <div><blockquote type="cite" style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br class="m_825998565340295454Apple-interchange-newline">On Dec 1, 2017, at 08:20, Gervase Markham <<a href="mailto:[email protected]" target="_blank">[email protected]</a>> wrote:<br><br>Hi Dylan,<br><br>Thanks for this - it's good to see some progress on defining what we are<br>going to be doing :-)<br><br>On 30/11/17 20:36, Dylan Hardison wrote:<br><blockquote type="cite">1. Significant changes to BMO must *not* be required.<br>1.1. No requiring perl 5.14, though nothing prevents us from working *better* on modern perls.<br></blockquote><br>What are the current Perl requirements for stable, trunk and BMO?<br><br>What is the objection to updating the version of Perl we require?<br><br></blockquote><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">We declare a min version in our code, and this declaration changes the syntax to some degree.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">For instance, in trunk we have use 5.14.0, which also enables strict mode too (so use strict is not needed).</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">BMO is targeting 5.10.1. It also runs under 5.16 quite well, because 5.16 is used by version-control-tools,</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">and it also runs under 5.24 and 5.26 just fine. But we can't rely on features from those until BMO production is migrated.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">In about six months I suspect BMO will be running on alpine linux and perl 5.26.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">I very much want to use only the supported (by the perl community) versions of perl, which is just "the last two versions",</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">but the reality is that I can't upgrade overnight.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">So for harmony, I'd like to have the minimum version be 5.10.1.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">I plan on porting<span class="m_825998565340295454Apple-converted-space"> </span></span><a href="https://github.com/mozilla-bteam/bmo-systems" style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank" data-saferedirecturl="https://www.google.com/url?hl=en&q=https://github.com/mozilla-bteam/bmo-systems&source=gmail&ust=1515101777340000&usg=AFQjCNElQ6JBpIarGRvnOKOmHHTG5STAlQ">https://github.com/<wbr>mozilla-bteam/bmo-systems</a><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important"><span class="m_825998565340295454Apple-converted-space"> </span>to upstream bugzilla as well, and<span class="m_825998565340295454Apple-converted-space"> </span></span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite" style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite">1.2. The usernames != login patch has to be backed out (someone started this, and I've asked gerv to review it on GitHub)<br></blockquote><br>Remind us all why this needs to happen?<br><br>Have we shipped this code to anyone?<br></blockquote><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">People running the master branch are definitely using it.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">The problems are a few:</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">it's possible for the DB to be out of sync with the parameter,</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">and if you're registering users when out of sync "strange" things could happen.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">For BMO the plan is to merely lax the requirement on the login_name field, after adding (multiple) email addresses to the account.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">This is similar to what many other platforms do.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1372631" style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank" data-saferedirecturl="https://www.google.com/url?hl=en&q=https://bugzilla.mozilla.org/show_bug.cgi?id%3D1372631&source=gmail&ust=1515101777340000&usg=AFQjCNHPSfEgjkzEiWGo2iMZe2UAELC35g">https://bugzilla.mozilla.org/<wbr>show_bug.cgi?id=1372631</a><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite" style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br><blockquote type="cite">2. We are going to follow <a href="https://rfc.zeromq.org/spec:42/C4/" target="_blank" data-saferedirecturl="https://www.google.com/url?hl=en&q=https://rfc.zeromq.org/spec:42/C4/&source=gmail&ust=1515101777340000&usg=AFQjCNGmoSy50NFYFfqFTlGV44MkzlbuXQ">https://rfc.zeromq.org/spec:<wbr>42/C4/</a> with the understanding that "Platform issue tracker" refers to <a href="http://bugzilla.mozilla.org" target="_blank" data-saferedirecturl="https://www.google.com/url?hl=en&q=http://bugzilla.mozilla.org&source=gmail&ust=1515101777340000&usg=AFQjCNEhkM3LfnV2X8BhffJ0v5iHzVw7hQ">bugzilla.mozilla.org</a><br></blockquote><br>What is your goal here? What about our current development model is<br>broken and needs fixing? Are there specific bits of this rather long<br>document which you are particularly concerned we adopt?<br><br><blockquote type="cite">3. All this work will happen to the "harmony" branch, and we'll continue to not touch 'master' to not break anyone that happens to be using it.<br></blockquote><br>I assume "harmony" will be a branch in <a href="http://github.com/bugzilla/bugzilla?" target="_blank" data-saferedirecturl="https://www.google.com/url?hl=en&q=http://github.com/bugzilla/bugzilla?&source=gmail&ust=1515101777340000&usg=AFQjCNFvxYj2vDQ__JcrcAuhfbWcTH8pvg">http://github.com/bugzilla/<wbr>bugzilla?</a><br><br>Will "harmony" start from master, stable, or from the BMO codebase?<br><br>I was rather expecting to start with the BMO code and work back towards<br>Bugzilla compatibility, rather than starting with master and working<br>towards BMO compatibility. The former certainly seems like it would be<br>easier to do...<br><br><blockquote type="cite">We are not in the business of packaging, there are too many combinations to worry about all of them.<br>People are welcome to help with packaging Bugzilla 6 / Harmony on anything, and nothing drastic will change<br>there. But as for releasable products, there are two channels that we must support:<br><br>1. A runnable docker container, based on Alpine linux<br></blockquote><br>I have no particular objection, but why Alpine Linux? What is that?<br></blockquote><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">A very small linux distro and the de-facto base image used by high-quality docker containers.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite" style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br><blockquote type="cite">2. A checkout from a tagged commit from GitHub.<br><br>The release process for Bugzilla Harmony will amount to tagging a commit (from the Harmony branch, more on that later).<br></blockquote><br>By "release process", do you mean "the process which result in the thing<br>we call e.g. Bugzilla 6.0"? Or are you talking about some testable<br>milestones we might ship along the way?<br><br></blockquote><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">Only the former. I'm going for continuous releases. I'm never going to have time for the other release process.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite" style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite">The release notes should be exactly the commit messages. Part of reviewing a PR is making sure the commit messages tell the appropriate story.<br></blockquote><br>I don't think this particular point is going to fly. It means you can't<br>really tell any story which spans multiple commits, and it means you<br>won't be picking out particular features as worth promoting. Doing<br>things this way will just result in pretty useless release notes. I<br>understand and agree with your desire to reduce the work involved in<br>shipping a release, but I think this is an over-economy.<br></blockquote><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">You can ignore a subset of commits -- I use this to build the announcements for BMO for the last 4 years.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">I also think with a continuous release process it is less interesting.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">We can say "pushing built images is not a release", but these non-releases are the only thing I'm committed to doing or supporting.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite" style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br><blockquote type="cite">Commits / Reviews / Pull Requests:<br><br>Read the C4 document, that is what contributing to Bugzilla's harmony branch should be like.<br></blockquote><br>That is a somewhat intimidating statement; see my question above. We<br>have been discussing a significant change to _what_ we are building; a<br>significant change to _how_ we are building it is somewhat of a bolt<br>from the blue. I would very much appreciate it if you were to explain<br>all this a bit more.<br><br></blockquote><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">The existing process has not worked, it's burdensome. The C4 process is effective</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">for a variety of successful projects.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">That document gives clear expectations for a lot of situations and encourages patches to actually land.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">I think that's something important.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite" style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite">4. Revert the REST API in favor of the (older) system that BMO is still using.<br></blockquote><br>Why is that necessary? Cannot a new, improved API and the old one live<br>in parallel?<br><br></blockquote><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">(explained upthread)</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite" style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite">5. Ensure a database created by 4.2, 5.0, or the master branch can be "upgraded" to from the harmony branch.<br></blockquote><br>I think you mean the other way around :-)<br></blockquote><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">yeah.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><blockquote type="cite" style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br><blockquote type="cite">10. Port GitHubAuth (this has already been done!)<br></blockquote><br>Surely the harmony branch needs eventually to support all BMO's extensions?<br><br></blockquote><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">Absolutely!</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">The reason harmony is starting from 5.0 is that the other major stake-holder is running (or will be shortly) 5.0 (RedHat).</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">I hope they open up their fork's repo, and I will continue to hope for that.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">I'm already going to be asking them if they can back-out on multiple bug aliases.</span><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><br style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Menlo-Regular;font-size:11px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">Handling the conflicts between BMO and 5.0 is a burden I am able to bear, so I won't ask my RedHat friends to shoulder it.</span></div> </body></html> --------------070007090402000006090305--