This is a bug fix pre-release, it seems we might have accidently broken an API between version 0.31 and 1.32. So this should address the issue and ensuring backwards compatibility.
We aim for stability, so this is regarded as a bug and we should ensure backwards compatibility.
The release should be on CPAN now. It does however not contain the changes from pre-release 1_33_2, the functionality will not be present until the next pre-release or release until the changes have sunk in and have been merged into trunk.
The bug situation put me in a situation as release manager I have not been before, so I simply followed my intuition, since I do not know what the best practice is.
In a work towards release 1.33, the next public release, we are making developer releases, like 1.33_2 and the never released 1.33_1. Both release where based on the same branch from 1.32.
Then a bug situation occurs and we want to create a bug fix pre-release, so the bug reporter can evaluate the proposed fix.
So I made a branch from 1.32 again and implemented the fix and release it as 1.33_3, even though it does not contain any of the changes from the branch from which 1.33_1 and 1.33_2 was released.
Is this the correct way? – or is there a better way?
0 Comments.