Re: [ros-dev] New ideas added to GSoC Ideas list

[Can Tasan]

Wine still maintains and even improves Windows 3.x support! I hope they don't 
give up!

Can we use Wine code while implementing WoW16?
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] New ideas added to GSoC Ideas list

[Can Tasan]

Wine still maintains and even improves Windows 3.x support! I hope they don't 
give up!

Can we use Wine code while implementing WoW16?
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] New ideas added to GSoC Ideas list

[David Quintana (gigaherz)]

That second Windows should have been ros.

On 17 March 2017 at 01:25, David Quintana (gigaherz) 
wrote:

> Running windows inside a vdm window isn't the same as running the apps
> directly in windows, as if they were native apps.
>
> On 17 March 2017 at 01:07, Javier Agustìn Fernàndez Arroyo <
> elh...@gmail.com> wrote:
>
>> some people have had success in running Win 3.1 under ReactOS thanks to
>> NTDVM, so win3.1 apps can be run too :)
>>
>> On Thu, Mar 16, 2017 at 11:49 PM, David Quintana (gigaherz) <
>> gigah...@gmail.com> wrote:
>>
>>> That's not true. NTVDM is not WoW16. NTVDM is just DOS support. In order
>>> to support 16bit (windows 3.1) applications, a whole other system is needed.
>>>
>>> On 16 March 2017 at 23:37, Javier Agustìn Fernàndez Arroyo <
>>> elh...@gmail.com> wrote:
>>>
 "-Implementing WoW16 support. I suppose that'll draw attention." -->
 NTVDM, already done :)

 "Working on DirectX support: bringing new features, fixing bugs,
 optimising, if possible fixing some driver issues..." ---> ReactX, would be
 great!

 On Thu, Mar 16, 2017 at 2:28 PM, Thomas Faber  wrote:

> I can tell you some possible next steps:
> - x64: implement PAE support in the 32 bit kernel
> - SMP: Implement resource translators and arbiters (I have some
> initial work for this somewhere)
> - Also SMP: build a CONFIG_SMP kernel (with some hack to use the
> regular HAL) and debug any issues coming from broken spinlock usage
>
> On March 16, 2017 5:50:39 AM EDT, Colin Finck 
> wrote:
>>
>> Am 16.03.2017 um 00:03 schrieb Huw Campbell:
>>
>>>  SMP or 64 bit processor support would be great. Too hard?
>>>
>>
>> I think that's too much for a single GSoC student. But we also keep
>> saying this for a long time... The result is that everybody is afraid of
>> those "big topics".
>>
>> What we need is some kernel dev looking into these topics and giving a
>> rough overview what needs to be done and in what places. Then we can
>> have a roadmap and split the work up into smaller tasks that are even
>> doable by GSoC students.
>>
>> If nobody makes this first step, we will never have SMP or x64 CPU
>> support. People also kept saying that full printer support is too much
>> for a 6-month bachelor thesis, and they were right, but nevertheless I
>> was able to build the foundations and documentation in that
>> time.
>> And now I could guide everyone interested how to continue on achieving
>> full printing support.
>>
>>
>> - Colin
>>
>> --
>>
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>>
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>


 ___
 Ros-dev mailing list
 Ros-dev@reactos.org
 http://www.reactos.org/mailman/listinfo/ros-dev

>>>
>>>
>>> ___
>>> Ros-dev mailing list
>>> Ros-dev@reactos.org
>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>
>>
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] New ideas added to GSoC Ideas list

[David Quintana (gigaherz)]

Running windows inside a vdm window isn't the same as running the apps
directly in windows, as if they were native apps.

On 17 March 2017 at 01:07, Javier Agustìn Fernàndez Arroyo  wrote:

> some people have had success in running Win 3.1 under ReactOS thanks to
> NTDVM, so win3.1 apps can be run too :)
>
> On Thu, Mar 16, 2017 at 11:49 PM, David Quintana (gigaherz) <
> gigah...@gmail.com> wrote:
>
>> That's not true. NTVDM is not WoW16. NTVDM is just DOS support. In order
>> to support 16bit (windows 3.1) applications, a whole other system is needed.
>>
>> On 16 March 2017 at 23:37, Javier Agustìn Fernàndez Arroyo <
>> elh...@gmail.com> wrote:
>>
>>> "-Implementing WoW16 support. I suppose that'll draw attention." -->
>>> NTVDM, already done :)
>>>
>>> "Working on DirectX support: bringing new features, fixing bugs,
>>> optimising, if possible fixing some driver issues..." ---> ReactX, would be
>>> great!
>>>
>>> On Thu, Mar 16, 2017 at 2:28 PM, Thomas Faber 
>>> wrote:
>>>
 I can tell you some possible next steps:
 - x64: implement PAE support in the 32 bit kernel
 - SMP: Implement resource translators and arbiters (I have some initial
 work for this somewhere)
 - Also SMP: build a CONFIG_SMP kernel (with some hack to use the
 regular HAL) and debug any issues coming from broken spinlock usage

 On March 16, 2017 5:50:39 AM EDT, Colin Finck 
 wrote:
>
> Am 16.03.2017 um 00:03 schrieb Huw Campbell:
>
>>  SMP or 64 bit processor support would be great. Too hard?
>>
>
> I think that's too much for a single GSoC student. But we also keep
> saying this for a long time... The result is that everybody is afraid of
> those "big topics".
>
> What we need is some kernel dev looking into these topics and giving a
> rough overview what needs to be done and in what places. Then we can
> have a roadmap and split the work up into smaller tasks that are even
> doable by GSoC students.
>
> If nobody makes this first step, we will never have SMP or x64 CPU
> support. People also kept saying that full printer support is too much
> for a 6-month bachelor thesis, and they were right, but nevertheless I
> was able to build the foundations and documentation in that
> time.
> And now I could guide everyone interested how to continue on achieving
> full printing support.
>
>
> - Colin
>
> --
>
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
>
 --
 Sent from my Android device with K-9 Mail. Please excuse my brevity.

 ___
 Ros-dev mailing list
 Ros-dev@reactos.org
 http://www.reactos.org/mailman/listinfo/ros-dev

>>>
>>>
>>> ___
>>> Ros-dev mailing list
>>> Ros-dev@reactos.org
>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>
>>
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] New ideas added to GSoC Ideas list

[Javier Agustìn Fernàndez Arroyo]

some people have had success in running Win 3.1 under ReactOS thanks to
NTDVM, so win3.1 apps can be run too :)

On Thu, Mar 16, 2017 at 11:49 PM, David Quintana (gigaherz) <
gigah...@gmail.com> wrote:

> That's not true. NTVDM is not WoW16. NTVDM is just DOS support. In order
> to support 16bit (windows 3.1) applications, a whole other system is needed.
>
> On 16 March 2017 at 23:37, Javier Agustìn Fernàndez Arroyo <
> elh...@gmail.com> wrote:
>
>> "-Implementing WoW16 support. I suppose that'll draw attention." -->
>> NTVDM, already done :)
>>
>> "Working on DirectX support: bringing new features, fixing bugs,
>> optimising, if possible fixing some driver issues..." ---> ReactX, would be
>> great!
>>
>> On Thu, Mar 16, 2017 at 2:28 PM, Thomas Faber 
>> wrote:
>>
>>> I can tell you some possible next steps:
>>> - x64: implement PAE support in the 32 bit kernel
>>> - SMP: Implement resource translators and arbiters (I have some initial
>>> work for this somewhere)
>>> - Also SMP: build a CONFIG_SMP kernel (with some hack to use the regular
>>> HAL) and debug any issues coming from broken spinlock usage
>>>
>>> On March 16, 2017 5:50:39 AM EDT, Colin Finck  wrote:

 Am 16.03.2017 um 00:03 schrieb Huw Campbell:

>  SMP or 64 bit processor support would be great. Too hard?
>

 I think that's too much for a single GSoC student. But we also keep
 saying this for a long time... The result is that everybody is afraid of
 those "big topics".

 What we need is some kernel dev looking into these topics and giving a
 rough overview what needs to be done and in what places. Then we can
 have a roadmap and split the work up into smaller tasks that are even
 doable by GSoC students.

 If nobody makes this first step, we will never have SMP or x64 CPU
 support. People also kept saying that full printer support is too much
 for a 6-month bachelor thesis, and they were right, but nevertheless I
 was able to build the foundations and documentation in that
 time.
 And now I could guide everyone interested how to continue on achieving
 full printing support.


 - Colin

 --

 Ros-dev mailing list
 Ros-dev@reactos.org
 http://www.reactos.org/mailman/listinfo/ros-dev


>>> --
>>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>>>
>>> ___
>>> Ros-dev mailing list
>>> Ros-dev@reactos.org
>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>
>>
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] New ideas added to GSoC Ideas list

[Hermès BÉLUSCA-MAÏTO]

To be the most accurate, WoW16 is an addition to NTVDM. NTVDM alone provides 
16-bit emulation plus DOS support. WoW16 adds on top of that, Win 3.1 support 
(which is also 16-bit). WoW16 is implemented using wow32.dll (the 32-bit part 
that interfaces directly with NTVDM), wowexec.exe (the corresponding 16-bit 
part), krnl386.exe (the “kernel” of Win 3.1) and the thunk dlls/exes user, gdi …

 

De : Ros-dev [mailto:ros-dev-boun...@reactos.org] De la part de David Quintana 
(gigaherz)
Envoyé : jeudi 16 mars 2017 23:50
À : ReactOS Development List
Objet : Re: [ros-dev] New ideas added to GSoC Ideas list

 

That's not true. NTVDM is not WoW16. NTVDM is just DOS support. In order to 
support 16bit (windows 3.1) applications, a whole other system is needed.

 

On 16 March 2017 at 23:37, Javier Agustìn Fernàndez Arroyo  
wrote:

"-Implementing WoW16 support. I suppose that'll draw attention." --> NTVDM, 
already done :)

"Working on DirectX support: bringing new features, fixing bugs, optimising, if 
possible fixing some driver issues..." ---> ReactX, would be great!

 

On Thu, Mar 16, 2017 at 2:28 PM, Thomas Faber  wrote:

I can tell you some possible next steps:
- x64: implement PAE support in the 32 bit kernel
- SMP: Implement resource translators and arbiters (I have some initial work 
for this somewhere)
- Also SMP: build a CONFIG_SMP kernel (with some hack to use the regular HAL) 
and debug any issues coming from broken spinlock usage

On March 16, 2017 5:50:39 AM EDT, Colin Finck  wrote:

Am 16.03.2017 um 00:03 schrieb Huw Campbell:
 SMP or 64 bit processor support would be great. Too hard?

I think that's too much for a single GSoC student. But we also keep
saying this for a long time... The result is that everybody is afraid of
those "big topics".

What we need is some kernel dev looking into these topics and giving a
rough overview what needs to be done and in what places. Then we can
have a roadmap and split the work up into smaller tasks that are even
doable by GSoC students.

If nobody makes this first step, we will never have SMP or x64 CPU
support. People also kept saying that full printer support is too much
for a 6-month bachelor thesis, and they were right, but nevertheless I
was able to build the foundations and documentation in that
time.
And now I could guide everyone interested how to continue on achieving
full printing support.


- Colin


  _  


Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev


-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

 

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

 


___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

 

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] New ideas added to GSoC Ideas list

[David Quintana (gigaherz)]

That's not true. NTVDM is not WoW16. NTVDM is just DOS support. In order to
support 16bit (windows 3.1) applications, a whole other system is needed.

On 16 March 2017 at 23:37, Javier Agustìn Fernàndez Arroyo  wrote:

> "-Implementing WoW16 support. I suppose that'll draw attention." -->
> NTVDM, already done :)
>
> "Working on DirectX support: bringing new features, fixing bugs,
> optimising, if possible fixing some driver issues..." ---> ReactX, would be
> great!
>
> On Thu, Mar 16, 2017 at 2:28 PM, Thomas Faber 
> wrote:
>
>> I can tell you some possible next steps:
>> - x64: implement PAE support in the 32 bit kernel
>> - SMP: Implement resource translators and arbiters (I have some initial
>> work for this somewhere)
>> - Also SMP: build a CONFIG_SMP kernel (with some hack to use the regular
>> HAL) and debug any issues coming from broken spinlock usage
>>
>> On March 16, 2017 5:50:39 AM EDT, Colin Finck  wrote:
>>>
>>> Am 16.03.2017 um 00:03 schrieb Huw Campbell:
>>>
  SMP or 64 bit processor support would be great. Too hard?

>>>
>>> I think that's too much for a single GSoC student. But we also keep
>>> saying this for a long time... The result is that everybody is afraid of
>>> those "big topics".
>>>
>>> What we need is some kernel dev looking into these topics and giving a
>>> rough overview what needs to be done and in what places. Then we can
>>> have a roadmap and split the work up into smaller tasks that are even
>>> doable by GSoC students.
>>>
>>> If nobody makes this first step, we will never have SMP or x64 CPU
>>> support. People also kept saying that full printer support is too much
>>> for a 6-month bachelor thesis, and they were right, but nevertheless I
>>> was able to build the foundations and documentation in that
>>> time.
>>> And now I could guide everyone interested how to continue on achieving
>>> full printing support.
>>>
>>>
>>> - Colin
>>>
>>> --
>>>
>>> Ros-dev mailing list
>>> Ros-dev@reactos.org
>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>
>>>
>> --
>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
>
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] New ideas added to GSoC Ideas list

[Thomas Faber]

I can tell you some possible next steps:
- x64: implement PAE support in the 32 bit kernel
- SMP: Implement resource translators and arbiters (I have some initial work 
for this somewhere)
- Also SMP: build a CONFIG_SMP kernel (with some hack to use the regular HAL) 
and debug any issues coming from broken spinlock usage

On March 16, 2017 5:50:39 AM EDT, Colin Finck  wrote:
>Am 16.03.2017 um 00:03 schrieb Huw Campbell:
>> SMP or 64 bit processor support would be great. Too hard?
>
>I think that's too much for a single GSoC student. But we also keep
>saying this for a long time... The result is that everybody is afraid
>of
>those "big topics".
>
>What we need is some kernel dev looking into these topics and giving a
>rough overview what needs to be done and in what places. Then we can
>have a roadmap and split the work up into smaller tasks that are even
>doable by GSoC students.
>
>If nobody makes this first step, we will never have SMP or x64 CPU
>support. People also kept saying that full printer support is too much
>for a 6-month bachelor thesis, and they were right, but nevertheless I
>was able to build the foundations and documentation in that time.
>And now I could guide everyone interested how to continue on achieving
>full printing support.
>
>
>- Colin
>
>___
>Ros-dev mailing list
>Ros-dev@reactos.org
>http://www.reactos.org/mailman/listinfo/ros-dev

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] JIRA/FishEye upgrade on March 8

[David Quintana (gigaherz)]

No worries. Getting the thing setup correctly is worth any wait.

On 16 March 2017 at 10:39, Colin Finck  wrote:

> Hi again!
>
> Mark's commit yesterday has revealed a misconfiguration of the FishEye
> indexing. Namely it only indexed source code files up to 100 KB and his
> edited freetype.c was 136 KB. Looking into our repository, we have
> source code files up to 1 MB.
>
> Unfortunately, the only way to fix this is changing the limit and
> letting FishEye reindex the repository. I have set the limit to 5 MB now
> to be on the safe side and launched the reindexing. FishEye information
> about the "reactos" repo is unavailable during that time.
>
> I expect general source code information to come back in a couple of
> hours. Indexing all diff information takes a little longer and I expect
> it to be done by the beginning of next week.
>
> Sorry for the inconveniences, but I better get basic things right before
> we have to live with them for a long time.
>
> - Colin
>
>
> Am 09.03.2017 um 20:11 schrieb Colin Finck:
> > Hi all!
> >
> > FishEye is back online as well now and currently indexing our
> > repository. Due to the better performance of the new server, it does so
> > nicely without taking down the entire JIRA and FishEye instances :)
> >
> > From my side, the entire upgrade is done now and all major bugs should
> > have been fixed.
> > If you still notice regressions, please report them! Note that some of
> > them may need to be reported to Atlassian though as we basically use
> > vanilla JIRA and FishEye installations.
> >
> > Cheers,
> >
> > Colin
> >
> >
> > Am 08.03.2017 um 15:57 schrieb Colin Finck:
> >> Hi all!
> >>
> >> I have successfully upgraded JIRA to the latest version 7.3.2 and
> >> https://jira.reactos.org is back up!
> >> Unfortunately, we already had the first regression report 15 minutes
> >> later: https://jira.reactos.org/browse/ONLINE-682 :(
> >>
> >> Please check it out and tell me if anything else regressed.
> >> I can try to fix any regressions tomorrow or we have to bring them to
> >> Atlassian's attention.
> >>
> >> FishEye/Crucible continues to be the hard customer again and I probably
> >> won't get it fully upgraded today. More will follow tomorrow.
> >>
> >> Cheers,
> >>
> >> Colin
> >>
> >>
> >> Am 24.02.2017 um 19:35 schrieb Colin Finck:
> >>> Hi all!
> >>>
> >>> Let me announce a definite date for our JIRA/FishEye upgrade:
> >>>
> >>>Wednesday, March 8, around 9:00 UTC
> >>>
> >>> Expect downtimes of several hours at https://code.reactos.org and
> >>> https://jira.reactos.org around this time.
> >>>
> >>> I can say for sure that I will have enough time on this day and the
> >>> following to deal with all possible incidents that could happen during
> >>> the complex upgrade.
> >>> This also allows me to get direct in-person feedback from all the devs
> >>> attending CLT on the weekend after that :)
> >>>
> >>> The upgrade to JIRA 7.x is a major one, and Atlassian recommends
> >>> everyone to have a look at the new features:
> >>> https://confluence.atlassian.com/migration/jira-7/server_
> jira_product-changes
> >>>
> >>> Best regards,
> >>>
> >>> Colin
> >>>
> >>> ___
> >>> Ros-dev mailing list
> >>> Ros-dev@reactos.org
> >>> http://www.reactos.org/mailman/listinfo/ros-dev
> >>>
> >>
> >> ___
> >> Ros-dev mailing list
> >> Ros-dev@reactos.org
> >> http://www.reactos.org/mailman/listinfo/ros-dev
> >>
> >
> > ___
> > Ros-dev mailing list
> > Ros-dev@reactos.org
> > http://www.reactos.org/mailman/listinfo/ros-dev
> >
>
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>
___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] New ideas added to GSoC Ideas list

[Colin Finck]

Am 16.03.2017 um 00:03 schrieb Huw Campbell:
> SMP or 64 bit processor support would be great. Too hard?

I think that's too much for a single GSoC student. But we also keep
saying this for a long time... The result is that everybody is afraid of
those "big topics".

What we need is some kernel dev looking into these topics and giving a
rough overview what needs to be done and in what places. Then we can
have a roadmap and split the work up into smaller tasks that are even
doable by GSoC students.

If nobody makes this first step, we will never have SMP or x64 CPU
support. People also kept saying that full printer support is too much
for a 6-month bachelor thesis, and they were right, but nevertheless I
was able to build the foundations and documentation in that time.
And now I could guide everyone interested how to continue on achieving
full printing support.


- Colin

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev

Re: [ros-dev] JIRA/FishEye upgrade on March 8

[Colin Finck]

Hi again!

Mark's commit yesterday has revealed a misconfiguration of the FishEye
indexing. Namely it only indexed source code files up to 100 KB and his
edited freetype.c was 136 KB. Looking into our repository, we have
source code files up to 1 MB.

Unfortunately, the only way to fix this is changing the limit and
letting FishEye reindex the repository. I have set the limit to 5 MB now
to be on the safe side and launched the reindexing. FishEye information
about the "reactos" repo is unavailable during that time.

I expect general source code information to come back in a couple of
hours. Indexing all diff information takes a little longer and I expect
it to be done by the beginning of next week.

Sorry for the inconveniences, but I better get basic things right before
we have to live with them for a long time.

- Colin


Am 09.03.2017 um 20:11 schrieb Colin Finck:
> Hi all!
> 
> FishEye is back online as well now and currently indexing our
> repository. Due to the better performance of the new server, it does so
> nicely without taking down the entire JIRA and FishEye instances :)
> 
> From my side, the entire upgrade is done now and all major bugs should
> have been fixed.
> If you still notice regressions, please report them! Note that some of
> them may need to be reported to Atlassian though as we basically use
> vanilla JIRA and FishEye installations.
> 
> Cheers,
> 
> Colin
> 
> 
> Am 08.03.2017 um 15:57 schrieb Colin Finck:
>> Hi all!
>>
>> I have successfully upgraded JIRA to the latest version 7.3.2 and
>> https://jira.reactos.org is back up!
>> Unfortunately, we already had the first regression report 15 minutes
>> later: https://jira.reactos.org/browse/ONLINE-682 :(
>>
>> Please check it out and tell me if anything else regressed.
>> I can try to fix any regressions tomorrow or we have to bring them to
>> Atlassian's attention.
>>
>> FishEye/Crucible continues to be the hard customer again and I probably
>> won't get it fully upgraded today. More will follow tomorrow.
>>
>> Cheers,
>>
>> Colin
>>
>>
>> Am 24.02.2017 um 19:35 schrieb Colin Finck:
>>> Hi all!
>>>
>>> Let me announce a definite date for our JIRA/FishEye upgrade:
>>>
>>>Wednesday, March 8, around 9:00 UTC
>>>
>>> Expect downtimes of several hours at https://code.reactos.org and
>>> https://jira.reactos.org around this time.
>>>
>>> I can say for sure that I will have enough time on this day and the
>>> following to deal with all possible incidents that could happen during
>>> the complex upgrade.
>>> This also allows me to get direct in-person feedback from all the devs
>>> attending CLT on the weekend after that :)
>>>
>>> The upgrade to JIRA 7.x is a major one, and Atlassian recommends
>>> everyone to have a look at the new features:
>>> https://confluence.atlassian.com/migration/jira-7/server_jira_product-changes
>>>
>>> Best regards,
>>>
>>> Colin
>>>
>>> ___
>>> Ros-dev mailing list
>>> Ros-dev@reactos.org
>>> http://www.reactos.org/mailman/listinfo/ros-dev
>>>
>>
>> ___
>> Ros-dev mailing list
>> Ros-dev@reactos.org
>> http://www.reactos.org/mailman/listinfo/ros-dev
>>
> 
> ___
> Ros-dev mailing list
> Ros-dev@reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
> 

___
Ros-dev mailing list
Ros-dev@reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev