[issue tracker] back porting 4 to 3
Hi, When there are issues that people wan to have back ported, the easiest (which worked very nicely last year) is this: 1) add the âback portâ issue as the *parent* of the main issue tracker entry. 2) make sure to do a slice early, itâs very easy to do when it is not yet integrated in Pharo4 (by looking at the diff). Issue 13494: Backport Pharo3 Issue 13494: some fixe â> Issue 13494: some fix Then first the slice will be validated on Pharo4, then it will get integrated there. After that, the Issue for Pharo3 will get validate by the monkey, and the is ready integration. This makes sure that fixes are put to use and validated in Pharo4 before we even think about adding them to the stable release. Marcus
Marcus Denker wrote:
Hi,
When there are issues that people wan to have back ported, the easiest (which worked very nicely last year) is this:
1) add the âback portâ issue as the *parent* of the main issue tracker entry. 2) make sure to do a slice early, itâs very easy to do when it is not yet integrated in Pharo4 (by looking at the diff).
Issue 13494: Backport Pharo3 Issue 13494: some fixe â> Issue 13494: some fix
Then first the slice will be validated on Pharo4, then it will get integrated there. After that, the Issue for Pharo3 will get validate by the monkey, and the is ready integration.
This makes sure that fixes are put to use and validated in Pharo4 before we even think about adding them to the stable release.
Marcus
nice idea
Marcus Denker-4 wrote
When there are issues that people wan to have back ported...
We should save this procedure in a more permanent place... ----- Cheers, Sean -- View this message in context: http://forum.world.st/issue-tracker-back-porting-4-to-3-tp4762606p4762613.ht... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
On 11 Jun 2014, at 14:59, Sean P. DeNigris <sean@clipperadams.com> wrote:
Marcus Denker-4 wrote
When there are issues that people wan to have back ported...
We should save this procedure in a more permanent place...
Indeed⦠I will put it somewhere.
----- Cheers, Sean -- View this message in context: http://forum.world.st/issue-tracker-back-porting-4-to-3-tp4762606p4762613.ht... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
On Sun, Sep 21, 2014 at 3:42 AM, Ben Coman <btc@openinworld.com> wrote:
Marcus Denker wrote:
On 11 Jun 2014, at 14:59, Sean P. DeNigris <sean@clipperadams.com> <sean@clipperadams.com> wrote:
Marcus Denker-4 wrote
When there are issues that people wan to have back ported...
We should save this procedure in a more permanent place...
Indeed⦠I will put it somewhere.
I think this is a really good idea, but there is some complexity in that an application uses those methods backported into the latest Pharo 3 will not be compatible with the Pharo 3 "release". Is ConfigurationOfPharo3 something that an application can depend on to bring these backported methods into an existing Pharo3 image ? Perhaps that should be mentioned in that procedure. And maybe also that should be part of a default template in Versioneer?
We should do something that is not too complex. Marcus
participants (3)
-
Ben Coman -
Marcus Denker -
Sean P. DeNigris