[Pulp-dev] MODIFIED redmine issues for 3.0 beta

Ina Panova ipanova at redhat.com
Tue May 15 10:03:06 UTC 2018

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
> released.
> 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?
> Thanks,
> Dennis
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20180515/d50cc3b2/attachment.htm>

More information about the Pulp-dev mailing list