packit icon indicating copy to clipboard operation
packit copied to clipboard

Published 20 hours ago • verified publisher icon packit

Plan Packit 1.0

Open csomh opened this issue 2 years ago • 3 comments

Prepare a plan how we are going to release Packit 1.0. Some (but not all) of the questions that are looking for answers:

How branching is going to look like in packit/packit?

We discussed to create a branch for 0.X and continue developing 1.0 on the main branch. Is this what we want to stick to? What should be the rule of thumb for adding fixes to 0.X?

What are the changes needed in the Fedora release process?

Because 1.0 is going to introduce backwards incompatible changes, it should be released first in Rawhide (And maybe 38—is it too late for that?), while 0.X is kept in current stable Fedora releases. How should the release process be updated to support this?

How and what are we going to build in Copr?

In packit/packit-stable and packit/packit-dev?

What version are we going to use in Packit Service?

Packit 1.0 will introduce backwards incompatible changes. How should we transition so that users get impacted as little as possible?

How are we going to communicate the change with our users?

The upgrade in Fedora shouldn't be an issue if we respect Fedora rules. How should the service be handled?

What should we prepare with to help users in the transition?

This is mostly relevant for Service users, who could see jobs failing b/c of outdated configuration options or changed behaviour.

Select and lock the set of issues in the 1.0 milestone

So we know exactly what work is ahead of us.

csomh avatar Feb 09 '23 11:02 csomh

A wild idea: we could do a hackfest after devconf.cz 2023 and resolve all the issues in the milestone, release 1.0 to rawhide only, keep building in our copr projects as usual.

For service, we should estimate what exact changes need to be done (i.e. deprecate packit.json via check runs) and communicate those.

TomasTomecek avatar Feb 10 '23 13:02 TomasTomecek

We have discussed on today's architecture, and we do not have any hard requirements for the release.

TODO:

  • [ ] revisit the points in the description, do what is still relevant
  • [ ] check the deprecated config options that we should drop before 1.0.0
  • [ ] revisit the issues from https://github.com/packit/packit/milestone/7, keep only the blocking ones

lbarcziova avatar Jul 25 '24 08:07 lbarcziova