|
Date: Wed, 10 Feb 2016 22:14:58 +0100
|
|
From: rbarlow@redhat.com
|
|
To: dropbox+pulp+c71e+pulp@plan.io
|
|
Message-ID: <56bba852e227d_3d953fb2c650fa2454786@gemini.mail>
|
|
in-reply-to: redmine.journal-8693.20160210162213.a3a2c75596eff652@plan.io
|
|
Subject: Re: [Pulp - Story #1639] As a developer, I can search Redmine for
|
|
issues that need to be done for a given Pulp distribution
|
|
Mime-Version: 1.0
|
|
Content-Type: text/plain;
|
|
charset=utf-8
|
|
Content-Transfer-Encoding: quoted-printable
|
|
Content-Disposition: inline
|
|
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23
|
|
X-HE-Spam-Level: ------
|
|
X-HE-Spam-Score: -6.0
|
|
X-HE-Spam-Report: Content analysis details: (-6.0 points) pts rule name
|
|
description ---- ----------------------
|
|
-------------------------------------------------- -5.0 RCVD_IN_DNSWL_HI RBL:
|
|
Sender listed at http://www.dnswl.org/, high trust [209.132.183.28 listed in
|
|
list.dnswl.org] -1.0 ENCRYPTED_MESSAGE Message is encrypted, not likely to be
|
|
spam
|
|
X-HE-SPF: PASSED
|
|
|
|
On Wed, Feb 10, 2016 at 05:22:14PM +0100, Pulp wrote:
|
|
> I believe that my proposed "Target Platform Release" meets this goal, b=
|
|
ut breaks current automation so for now we must suffer. This name would b=
|
|
e a bit of a compromise with Redmine: Ideally, I think the field would be=
|
|
"Target Release" in platform, and "Pulp Distribution" in plugins, but Re=
|
|
dmine doesn't let us to fun things like that. I think that going with "Ta=
|
|
rget Platform Release" gives us a field name with clear meaning in both c=
|
|
ontexts. In the context of plugin trackers, the purpose of a "Target Dist=
|
|
ribution" or "Pulp Distribution" field becomes less obvious to me, compar=
|
|
ed to "Target Platform Release". Maybe "Target Pulp Release" is better st=
|
|
ill, since the platform could be interpreted to mean something like "Fedo=
|
|
ra 23", or "RHEL 7", for example. Thoughts?
|
|
|
|
I like your proposed name "Target Platform Release". +1
|
|
|
|
> I love this idea, but think it's a separate story that depends on this =
|
|
story being completed.
|
|
|
|
+1, I'll file it if this gets traction.
|
|
> --- Please write your response above this line ---
|
|
> =
|
|
|
|
> Issue #1639 has been updated by semyers.
|
|
> =
|
|
|
|
> =
|
|
|
|
> rbarlow wrote:
|
|
> > I have a specific proposal for this: we could add a "Pulp distributio=
|
|
n" attribute to all of our subprojects that has versions like "2.8.0" (ba=
|
|
sically, the platform versions). Then all tickets have both a Target rele=
|
|
ase and a Pulp distribution target release (or similar name). Then, we ca=
|
|
n query this new field to find out what issues need to be fixed with 2.8.=
|
|
0, even for things that have their own version scheme (like Docker, Pytho=
|
|
n, OSTree, Kombu, Celery, etc.).
|
|
> =
|
|
|
|
> I believe that my proposed "Target Platform Release" meets this goal, b=
|
|
ut breaks current automation so for now we must suffer. This name would b=
|
|
e a bit of a compromise with Redmine: Ideally, I think the field would be=
|
|
"Target Release" in platform, and "Pulp Distribution" in plugins, but Re=
|
|
dmine doesn't let us to fun things like that. I think that going with "Ta=
|
|
rget Platform Release" gives us a field name with clear meaning in both c=
|
|
ontexts. In the context of plugin trackers, the purpose of a "Target Dist=
|
|
ribution" or "Pulp Distribution" field becomes less obvious to me, compar=
|
|
ed to "Target Platform Release". Maybe "Target Pulp Release" is better st=
|
|
ill, since the platform could be interpreted to mean something like "Fedo=
|
|
ra 23", or "RHEL 7", for example. Thoughts?
|
|
> =
|
|
|
|
> As mentioned in a meeting earlier today, changing the name of this fiel=
|
|
d will break automation. Brian should be commenting on that.
|
|
> =
|
|
|
|
> > These projects will also continue to use their own target release fie=
|
|
lds for convenience. We may even be able to automate the target release f=
|
|
ield so that it is automatically set correctly based on the distribution =
|
|
release. I.e., we know that the 2.8.0 will ship pulp-docker 2.0.0 - inste=
|
|
ad of relying on humans to do that, we could use some kind of cron script=
|
|
(perhaps the one we already use that maps bz to redmine?) to ensure that=
|
|
the target releases on the bugs are correct. This field would be used by=
|
|
users who want to know "which version of pulp-docker fixed bug xyz?"
|
|
> =
|
|
|
|
> I love this idea, but think it's a separate story that depends on this =
|
|
story being completed.
|
|
> =
|
|
|
|
> ----------------------------------------
|
|
> Story #1639: As a developer, I can search Redmine for issues that need =
|
|
to be done for a given Pulp distribution
|
|
> https://pulp.plan.io/issues/1639#change-8693
|
|
> =
|
|
|
|
> * Author: rbarlow
|
|
> * Status: NEW
|
|
> * Priority: Normal
|
|
> * Assignee: =
|
|
|
|
> * Category: =
|
|
|
|
> * Sprint/Milestone: =
|
|
|
|
> * Target Release: =
|
|
|
|
> * Backwards Incompatible: No
|
|
> * Groomed: No
|
|
> * Sprint Candidate: No
|
|
> * Tags: =
|
|
|
|
> * QA Contact: =
|
|
|
|
> * Bugzilla: =
|
|
|
|
> ----------------------------------------
|
|
> We need a way to do a single query in Redmine that can show us a priori=
|
|
tized list of issues that need to be done for a given Pulp distribution. =
|
|
It's important to note that Pulp is not just a platform, but it is also a=
|
|
distribution. We don't just distribute Pulp with a given version of Pul=
|
|
p, say 2.8, but we also distribute many other versions of packages that w=
|
|
e write and packages that we do not write. Thus, when we talk about Pulp =
|
|
2.8 we are sometime referring to Pulp the platform, but more often we are=
|
|
talking about Pulp the distribution. I.e., "we need to fix pulp-docker b=
|
|
ug xyz for 2.8" really means that we need to fix pulp-docker bug xyz for =
|
|
pulp-docker 2.0.0, which will be distributed with the Pulp 2.8 distributi=
|
|
on.
|
|
> =
|
|
|
|
> We can use the comments for specific implementation proposals, but the =
|
|
"done" criteria will be when developers can perform a single Redmine quer=
|
|
y to find out what needs to be done for a given Pulp release, such as "2.=
|
|
8".
|
|
> =
|
|
|
|
> =
|
|
|
|
> =
|
|
|
|
> --
|
|
> You have received this notification because you have either subscribed =
|
|
to or are involved in a project on Pulp Planio.
|
|
> To change your notification preferences, please click here: https://pul=
|
|
p.plan.io/my/account?tour=3Dmail_preferences
|
|
> =
|
|
|
|
> This notification was cheerfully delivered by https://plan.io
|
|
> =C2=A0
|
|
|
|
-- =
|
|
|
|
Randy Barlow
|
|
irc: bowlofeggs
|
.