Hi,
These are fixes to projects that are developped/maintained using their own
repository.
The idea is to commit there, mark it as “fixed upstream” and the maintainer
then pushes larger
batches back (using the configuration approach).
The idea was that this allows to speed up things by working in parallel and
shifting work the
maintainers, in practice though the sync back happens far to slow…
“if we just could do slice this would be fixed since 3 weeks” is often a good
summary of a
“fixed upstream” case...
Marcus
> On 18 Dec 2015, at 13:49, Juraj Kubelka <[email protected]> wrote:
>
> What is fixed-upstream tag about?
> https://pharo.fogbugz.com/f/filters/138/fixed-upstream
> <https://pharo.fogbugz.com/f/filters/138/fixed-upstream>
>
> Thanks,
> Juraj
>
>> 18. 12. 2015 v 9:35, Juraj Kubelka <[email protected]
>> <mailto:[email protected]>>:
>>
>> Thanks.
>>
>> I can see there are no issues with sprint tag. We will choose some; let’s
>> talk on Slack…
>>
>> Cheers,
>> Juraj
>>
>>> 18. 12. 2015 v 9:19, Marcus Denker <[email protected]
>>> <mailto:[email protected]>>:
>>>
>>> Hi,
>>>
>>> We are doing a sprint in Lille, too.
>>>
>>> But it is a bit special
>>>
>>> -> CI slaves do not connect. No builds possible
>>> -> Test runner fails, so committed changes can not be tested
>>>
>>> So a real sprint (where things can be integrated) is a bit difficult.
>>>
>>> I am trying to fix the CI….
>>>
>>>
>>>> On 18 Dec 2015, at 12:27, Juraj Kubelka <[email protected]
>>>> <mailto:[email protected]>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> We are having Pharo Sprint in about one hour. If anyone is aware of an
>>>> issue that is important to fix, we will appreciate if you mark it in
>>>> FogBugz by sprint tag or post it here.
>>>>
>>>> Thanks,
>>>> Juraj
>>>>
>>>> --
>>>> Juraj Kubelka
>>>
>>>
>>
>>
>
