-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Patch release r1.3 of CarrierBillingCheckout - to be shown in Fall24 release #124
Comments
I tried again to understand why the two release tracker for carrier-billing v0.3.1 and carrier-billing-refund v0.1.1 are not showing up within the table of the meta-release Fall24. To my understanding uses the table for filtering the two labels Will get fixed by camaraproject/.github#7 ... needs one approval before merge @tanjadegroot |
Found it finally: the new release tracker have there tables not in the "page properties macro" of Confluence, but in simple tables. Hence the "page properties report" macro can not collect the content from these release trackers. I propose to integrate the information of the additional release trackers into the original ones from the Fall24 release, as other patch releases have done as well. cc: @tanjadegroot |
I also found and corrected the bug which was indeed that the release tracker was missing the page properties macro. To avoid such issues, I would highly recommend that we document the patches on the existing release tracker. It is proposed to add update the existing release tracker as follows:
|
Problem description
CarrierBillingCheckout has done a path release in camaraproject/CarrierBillingCheckOut#193 without involvement of the Release Management team. The release itself looks good to me.
The team has created new release trackers for the patch versions of the API:
This approach makes sense, as it avoids to overwrite the information within version published originally within the meta-release. We should think about to define as the general approach: every public release should have its own release tracker.
Two remaining issues:
Expected action
Additional context
The text was updated successfully, but these errors were encountered: