we should add Pharo30 inbox
Hi we should add Pharo 30 inbox because many changes for 40 have been published there. Stef
On 29 May 2014, at 08:42, stepharo <stepharo@free.fr> wrote:
Hi
we should add Pharo 30 inbox because many changes for 40 have been published there.
Yes, for a while⦠or we just copy over all the slices. We need to start again to systematically do issue tracker: e.g. on an issue like that: put a note that the slice is in the wrong repo and a note: Next Action: copy slice to Pharo4 inbox. This way all these things get to be tiny 10 second actions that we can step by tiny step do efficiently. Marcus
On 29/5/14 09:45, Marcus Denker wrote:
On 29 May 2014, at 08:42, stepharo <stepharo@free.fr> wrote:
Hi
we should add Pharo 30 inbox because many changes for 40 have been published there.
Yes, for a while⦠or we just copy over all the slices.
We need to start again to systematically do issue tracker:
e.g. on an issue like that: put a note that the slice is in the wrong repo and a note: Next Action: copy slice to Pharo4 inbox.
I do not think that copying slice is a good idea. And I would refrain to create bug entries because it takes so much time handling them.
This way all these things get to be tiny 10 second actions that we can step by tiny step do efficiently.
Marcus
On 29 May 2014, at 11:57, stepharo <stepharo@free.fr> wrote:
On 29/5/14 09:45, Marcus Denker wrote:
On 29 May 2014, at 08:42, stepharo <stepharo@free.fr> wrote:
Hi
we should add Pharo 30 inbox because many changes for 40 have been published there.
Yes, for a while⦠or we just copy over all the slices.
We need to start again to systematically do issue tracker:
e.g. on an issue like that: put a note that the slice is in the wrong repo and a note: Next Action: copy slice to Pharo4 inbox.
I do not think that copying slice is a good idea. And I would refrain to create bug entries because it takes so much time handling them.
It is either a bug entry or a entry in my private TODO list. To me the only difference is that in case b) I am the only one who will act, while the issue tracker more people can do things. Marcus
On 29 May 2014, at 12:01, Marcus Denker <marcus.denker@inria.fr> wrote:
On 29 May 2014, at 11:57, stepharo <stepharo@free.fr> wrote:
On 29/5/14 09:45, Marcus Denker wrote:
On 29 May 2014, at 08:42, stepharo <stepharo@free.fr> wrote:
Hi
we should add Pharo 30 inbox because many changes for 40 have been published there.
Yes, for a while⦠or we just copy over all the slices.
We need to start again to systematically do issue tracker:
e.g. on an issue like that: put a note that the slice is in the wrong repo and a note: Next Action: copy slice to Pharo4 inbox.
I do not think that copying slice is a good idea. And I would refrain to create bug entries because it takes so much time handling them.
I added the inbox. But this is not enough⦠we would need to add the main repo, too, as for merging it needs the latest common ancestor (or maybe because we killed the 6MB of MC meta dataâ¦) Marcus
participants (2)
-
Marcus Denker -
stepharo