#8794 Unretire 27 packages... (was: unorphan)
Closed: Fixed 4 years ago by humaton. Opened 4 years ago by cipherboy.

  • Describe the issue

In order to keep resteasy alive, I'd like these packages to be unretired for now:

  • glassfish-management-api -- master
  • glassfish-gmbal -- master
  • java-oauth -- master
  • cli-parser -- master
  • jboss-jaspi-1.1-api -- master
  • jackson-dataformat-xml -- master
  • classmate -- master
  • simple -- master
  • mustache-java -- master
  • jackson-jaxrs-providers -- master
  • jboss-jaxrs-2.0-api -- master
  • jackson-modules-base -- master
  • glassfish-hk2 -- master
  • glassfish-pfl -- master
  • rxjava -- master
  • jersey -- master
  • picketbox-commons
  • mimepull -- master
  • netty3 -- master
  • paranamer -- master
  • jandex-maven-plugin -- master
  • grizzly -- master
  • grizzly-npn -- master

I'll likely re-orphan the ones I don't need after I've had time to sort through them all and trim down resteasy.

These packages were already unorphaned by @churchyard; now I'd like them to be unretired. :)

  • When do you need this? (YYYY/MM/DD)

2019/09/31 -- end of September would be nice.

  • When is this no longer needed or useful? (YYYY/MM/DD)

Always useful :)

  • If we cannot complete your request, what is the impact?

F32 will (eventually) break because resteasy will be removed by FTBFS policy, causing eventual dogtag-pki removal, causing eventual freeipa removal. The latter has self-selected as a critical Fedora component I'm told. :-)


Thanks for picking so many packages.

jsonp is owned by @jjelen

Giving rpms/glassfish-management-api to cipherboy
Giving rpms/glassfish-gmbal to cipherboy
Giving rpms/java-oauth to cipherboy
Giving rpms/picketbox to cipherboy
Giving rpms/cli-parser to cipherboy
Giving rpms/jboss-jaspi-1.1-api to cipherboy
Giving rpms/jackson-dataformat-xml to cipherboy
Giving rpms/classmate to cipherboy
Giving rpms/simple to cipherboy
Giving rpms/picketbox-xacml to cipherboy
Giving rpms/mustache-java to cipherboy
Giving rpms/jackson-jaxrs-providers to cipherboy
Giving rpms/jboss-jaxrs-2.0-api to cipherboy
Giving rpms/jackson-modules-base to cipherboy
Giving rpms/glassfish-hk2 to cipherboy
Giving rpms/glassfish-pfl to cipherboy
Giving rpms/rxjava to cipherboy
Giving rpms/jersey to cipherboy
Giving rpms/picketbox-commons to cipherboy
Giving rpms/mimepull to cipherboy
Giving rpms/jboss-connector-1.6-api to cipherboy
Giving rpms/netty3 to cipherboy
Giving rpms/paranamer to cipherboy
Giving rpms/jandex-maven-plugin to cipherboy
Giving rpms/grizzly to cipherboy
Giving rpms/grizzly-npn to cipherboy

Please assign all the bugzillas to you and close this ticket:

Ah my bad, @jjelen can keep jsonp. :)

Metadata Update from @cipherboy:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

@churchyard Do I need to go through re-reviews of all the packages with dead.package in master? Or can I request releng simply unblock master and push a git revert?

Most of these look like they're at the 6 week mark and not the 8 week mark such as jboss-jaxrs-2.0-api.

Metadata Update from @cipherboy:
- Issue status updated to: Open (was: Closed)

4 years ago

You need to unretire package with dead.package in master.

The procedure is to open a releng ticket for that (hopefully this one can serve as well if you rename it to "Unorphan/unretire 27 packages").

If the package has been retired for 8 weeks or more, yes, it needs to go through re-review. If the package has been retired for less than 8 weeks, it doesn't need to go trough re-review?

What packages do you need to unretire on what branches? (Note that I'm asking this, just so it is clear in this ticket, I cannot unretire packages.)

Note that the 6 weeks mark and the 8 weeks mark are counted separately.

A package that is orphaned for 6+ weeks is retired. A package that is retired (not orphaned) for 8+ weeks needs a new review. Hence in case when considering both deadlines, it's usually 14+ weeks after the package is orphaned before a re-review is needed.

@churchyard Ah I understand now, thanks :) Then yes, none of these need to be re-reviewed. I've clarified in the ticket that it is now an unRETIRE operation, and specified the branches. It looks like it was only ever master branches and no f31 branches were affected. :)

Metadata Update from @humaton:
- Issue assigned to humaton

4 years ago

This is a great opportunity to test my unretirement helper script, please give me a couple of hours.

@cipherboy all packages from the list should be unretired and unblocked in koji.
Please reopen this ticket if there are any leftovers.

Metadata Update from @humaton:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata