[Pulp-dev] pulpcore 3.4.0 release scheduled for May 27th

Tatiana Tereshchenko ttereshc at redhat.com
Wed May 20 07:17:13 UTC 2020

Hi Justin,

I think because we are trying to do time-based releases, we are not
aligning anything upfront. Just close to the release time, blockers are
being added to the release milestone, for the rest items milestone is set
at a release time.
To see what will end up in the upcoming release one can look at issues at
MODIFIED state. Here is the query https://tinyurl.com/y7ry4xoy (it excludes
installer and CI work, so it's easier to spot pulp features and bug fixes).

Maybe we should create a custom query in redmine for all projects -
something like "Upcoming feature release". The query will just include all
issues (except tests and pulp2) in MODIFIED state (though some bug
fixes might be released earlier, if Z release is planned).
What do you all think?


On Wed, May 20, 2020 at 3:08 AM Justin Sherrill <jsherril at redhat.com> wrote:

> Is it normal for things added/fixed between 3.3 and 3.4 to not show up in
> that version tracker?
> The item i'm thinking about is https://pulp.plan.io/issues/6591
> On 5/19/20 8:55 PM, Dennis Kliban wrote:
> Pulpcore 3.4.0 is scheduled to be released on May 27th. There are
> currently 3 issues that have been proposed as blockers for this release[0].
> Please respond to this thread with any other issues that should potentially
> be addressed in this release.
> [0] https://pulp.plan.io/versions/88
> _______________________________________________
> Pulp-dev mailing listPulp-dev at redhat.comhttps://www.redhat.com/mailman/listinfo/pulp-dev
> _______________________________________________
> 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/20200520/e147604a/attachment.htm>

More information about the Pulp-dev mailing list