That makes sense to me too, with a backward pointer (dependency) to
the previous release's ticket.
On Thu, Dec 1, 2022 at 9:35 PM Chris Johns wrote:
>
> Hi,
>
> Joel and I have been cleaning up the 6 tickets and some have been moved to 7
> (thanks) which may be appropriate however I am wondering about open ended
> tickets for a specific set of work and release notes. These tickets are really
> great for collecting commits for a specific change.
>
> The release notes are based on the tickets for a release and milestone. An
> open
> ended ticket for a specific task when part of release collects the related
> commits however moving that ticket to the next release moves the commits to
> that
> release's release notes and the current release does not see the commits in
> its
> release notes?
>
> Should the ticket be cloned (without comments?) to the next release and the
> one
> on the current release closed. It seems to make sense to me. The work is
> continuing however it is closed for the branch being release?
>
> Thanks
> Chris
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
