[Pulp-dev] MODIFIED redmine issues for 3.0 beta
rchan at redhat.com
Tue May 15 13:35:03 UTC 2018
A few use cases where it would be useful for Pulp 3 issues released in
a Beta would be considered closed are:
1. Sprint content
2. Your own queries on what is Open & assigned to you.
- Query can just be changed.
3. If a user is seeing an issue in Pulp 3 (or Pulp 2) - can they
easily find which functionality is available to them or not yet
As I understand it, this is only a change for Pulp 3 items? It may be
useful to keep the behaviour consistent in redmine.
On Tue, May 15, 2018 at 6:03 AM, Ina Panova <ipanova at redhat.com> wrote:
> If i am not mistaken as of now the person who takes care of a release needs
> to manually change the issue status.
> There is a possibility to select all the issues and actually move the status
> in 1 click. Do you think to automate this will pay off?
> I am fine to close issues as current release in case we set the target
> release specifically Beta, otherwise it sounds like it brings some
> There is a big period between Beta and GA and you never know what can happen
> to those set issues especially if they are targeted as GA.
> Ina Panova
> Software Engineer| Pulp| Red Hat Inc.
> "Do not go where the path may lead,
> go instead where there is no path and leave a trail."
> On Mon, May 14, 2018 at 7:03 PM, Dennis Kliban <dkliban at redhat.com> wrote:
>> Historically we would transition issues in Pulp's issue tracker from
>> MODIFIED to CLOSED - CURRENTRELEASE when a GA build went out the door. The
>> same approach is working against us for the duration of the Pulp 3.0 beta.
>> We have a large number of issues in MODIFIED state, but are considered
>> I propose that we transition issues to CLOSED - CURRENTRELEASE when they
>> have been shipped with a 3.0 beta.
>> Could we add automation to do this at release time?
>> What do you all think?
>> Pulp-dev mailing list
>> Pulp-dev at redhat.com
> Pulp-dev mailing list
> Pulp-dev at redhat.com
More information about the Pulp-dev