Release 4.1.4 - Can we add a script to the release to help user support in working around an issue?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Release 4.1.4 - Can we add a script to the release to help user support in working around an issue?

Peter Kovacs-2
Hello Jim,

Can we add following Script in the (Windows?) Bundle?

hanya wrote a python script which fixes spellcheck problems - see

Spell checker "red wriggly lines" - beta test fix at
https://forum.openoffice.org/en/forum/viewtopic.php?f=74&t=85529.

So User Support can advise to start the script for users in need.


All the best
Peter

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Release 4.1.4 - Can we add a script to the release to help user support in working around an issue?

Andrea Pescetti-2
Peter Kovacs wrote:
> Can we add following Script in the (Windows?) Bundle?
> hanya wrote a python script which fixes spellcheck problems - see
> Spell checker "red wriggly lines" - beta test fix at
> https://forum.openoffice.org/en/forum/viewtopic.php?f=74&t=85529.

If this is from hanya (I'm not sure since I don't know the forum
usernames) then hanya is a committer and he can add it to trunk, for a
possible backport. With the obvious exceptions, code that is not in
trunk can't be considered for 4.1.4.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Release 4.1.4 - Can we add a script to the release to help user support in working around an issue?

Jim Jagielski
Agreed.

> On Jun 13, 2017, at 1:01 PM, Andrea Pescetti <[hidden email]> wrote:
>
> Peter Kovacs wrote:
>> Can we add following Script in the (Windows?) Bundle?
>> hanya wrote a python script which fixes spellcheck problems - see
>> Spell checker "red wriggly lines" - beta test fix at
>> https://forum.openoffice.org/en/forum/viewtopic.php?f=74&t=85529.
>
> If this is from hanya (I'm not sure since I don't know the forum usernames) then hanya is a committer and he can add it to trunk, for a possible backport. With the obvious exceptions, code that is not in trunk can't be considered for 4.1.4.
>
> Regards,
>  Andrea.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Release 4.1.4 - Can we add a script to the release to help user support in working around an issue?

Marcus (OOo)
In reply to this post by Andrea Pescetti-2
Am 13.06.2017 um 19:01 schrieb Andrea Pescetti:

> Peter Kovacs wrote:
>> Can we add following Script in the (Windows?) Bundle?
>> hanya wrote a python script which fixes spellcheck problems - see
>> Spell checker "red wriggly lines" - beta test fix at
>> https://forum.openoffice.org/en/forum/viewtopic.php?f=74&t=85529.
>
> If this is from hanya (I'm not sure since I don't know the forum
> usernames) then hanya is a committer and he can add it to trunk, for a
> possible backport. With the obvious exceptions, code that is not in
> trunk can't be considered for 4.1.4.

assumed it's OK on trunk and 4.1.4, how do we integrate this into the
installation process?

Marcus


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Release 4.1.4 - Can we add a script to the release to help user support in working around an issue?

Andrea Pescetti-2
Marcus wrote:
> assumed it's OK on trunk and 4.1.4, how do we integrate this into the
> installation process?

I see it as an on-demand tool. So nothing would be added to the
installation process. A new menu item would be available for it (the
current solution uses the macro runner menu).

It seems, though, that the current implementation relies on being
executed from the user profile and this will probably not work for our
4.1.4 use case: I haven't checked, but I believe that the profile is
left unchanged by maintenance (4.1.x) updates. This should be
investigated though: there is likely a way to bundle it as a "shared"
script that would then be available even without touching the profile.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Release 4.1.4 - Can we add a script to the release to help user support in working around an issue?

Marcus (OOo)
Am 13.06.2017 um 23:24 schrieb Andrea Pescetti:

> Marcus wrote:
>> assumed it's OK on trunk and 4.1.4, how do we integrate this into the
>> installation process?
>
> I see it as an on-demand tool. So nothing would be added to the
> installation process. A new menu item would be available for it (the
> current solution uses the macro runner menu).
>
> It seems, though, that the current implementation relies on being
> executed from the user profile and this will probably not work for our
> 4.1.4 use case: I haven't checked, but I believe that the profile is
> left unchanged by maintenance (4.1.x) updates. This should be
> investigated though: there is likely a way to bundle it as a "shared"
> script that would then be available even without touching the profile.

an alternative would be to create a new Help menu entry (e.g., "Help -
Spell check fix"). This opens a webpage which provides a download link
to the file and a text with explainations/instructions: Why is it
needed, how to unpack/install/execute it, what is it going to do, etc.

Marcus


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Release 4.1.4 - Can we add a script to the release to help user support in working around an issue?

Peter Kovacs-4
Hello all,

John (in CC) suggested to add the Script of Hanya (also in CC) to the
Open Office Release as a first improvement.
On the discussion in this thread @dev declared only stuff that is in
trunc can be part of an release.
Since Hanya has comitter rights granted it was suggested he should be
the one commiting his script.

@Hanya: Do you believe that your script is stable enough to be added or
is there work to do to get it commited?
Can you commit your work, so we can add it for release?

@Jim (Release Manager):
What is the timeframe for you to get this script into 4.1.4. You only
stated that it has to be in svn, not until when and what the timeframe
is. My understanding is the current Version is close to a RC.

Hope this drives this topic a little further.

All the best
Peter

Am 13.06.2017 um 23:42 schrieb Marcus:

> Am 13.06.2017 um 23:24 schrieb Andrea Pescetti:
>> Marcus wrote:
>>> assumed it's OK on trunk and 4.1.4, how do we integrate this into the
>>> installation process?
>>
>> I see it as an on-demand tool. So nothing would be added to the
>> installation process. A new menu item would be available for it (the
>> current solution uses the macro runner menu).
>>
>> It seems, though, that the current implementation relies on being
>> executed from the user profile and this will probably not work for
>> our 4.1.4 use case: I haven't checked, but I believe that the profile
>> is left unchanged by maintenance (4.1.x) updates. This should be
>> investigated though: there is likely a way to bundle it as a "shared"
>> script that would then be available even without touching the profile.
>
> an alternative would be to create a new Help menu entry (e.g., "Help -
> Spell check fix"). This opens a webpage which provides a download link
> to the file and a text with explainations/instructions: Why is it
> needed, how to unpack/install/execute it, what is it going to do, etc.
>
> Marcus
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Release 4.1.4 - Can we add a script to the release to help user support in working around an issue?

Jim Jagielski
Yes, we are close to a release so I would recommend adding it as a
4.1.4. issue

> On Jun 18, 2017, at 3:58 AM, Peter Kovacs <[hidden email]> wrote:
>
> Hello all,
>
> John (in CC) suggested to add the Script of Hanya (also in CC) to the Open Office Release as a first improvement.
> On the discussion in this thread @dev declared only stuff that is in trunc can be part of an release.
> Since Hanya has comitter rights granted it was suggested he should be the one commiting his script.
>
> @Hanya: Do you believe that your script is stable enough to be added or is there work to do to get it commited?
> Can you commit your work, so we can add it for release?
>
> @Jim (Release Manager):
> What is the timeframe for you to get this script into 4.1.4. You only stated that it has to be in svn, not until when and what the timeframe is. My understanding is the current Version is close to a RC.
>
> Hope this drives this topic a little further.
>
> All the best
> Peter
>
> Am 13.06.2017 um 23:42 schrieb Marcus:
>> Am 13.06.2017 um 23:24 schrieb Andrea Pescetti:
>>> Marcus wrote:
>>>> assumed it's OK on trunk and 4.1.4, how do we integrate this into the
>>>> installation process?
>>>
>>> I see it as an on-demand tool. So nothing would be added to the installation process. A new menu item would be available for it (the current solution uses the macro runner menu).
>>>
>>> It seems, though, that the current implementation relies on being executed from the user profile and this will probably not work for our 4.1.4 use case: I haven't checked, but I believe that the profile is left unchanged by maintenance (4.1.x) updates. This should be investigated though: there is likely a way to bundle it as a "shared" script that would then be available even without touching the profile.
>>
>> an alternative would be to create a new Help menu entry (e.g., "Help - Spell check fix"). This opens a webpage which provides a download link to the file and a text with explainations/instructions: Why is it needed, how to unpack/install/execute it, what is it going to do, etc.
>>
>> Marcus
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Release 4.1.4 - Can we add a script to the release to help user support in working around an issue?

John Ha yahoo
In reply to this post by Peter Kovacs-4
Peter

See Spell checker "red wriggly lines" - beta test fix
<https://forum.openoffice.org/en/forum/viewtopic.php?f=74&t=85529>  
where three users with spell check problems have downloaded the python
script and reported back that it ran successfully.

I asked any who do run it to report back so hopefully we will get more
reports which should improve your confidence in releasing it.  78 people
have downloaded the script so far but only three have reported back.

  * /As requested, I have tried your Macro patch, and it has had the
    desired results, thank you./
  * /This saved my spellcheck. Thank you!/
  * /I came across this problem all of a sudden and it drives me crazy.
    I have been trying to fix it even to the point of uninstalling and
    reinstalling new version. To no luck. I came across this and WALLA
    it fixed. Thank You SO MUCH.//Thank Again/

John Harvey
On 18/06/2017 08:58, Peter Kovacs wrote:

> Hello all,
>
> John (in CC) suggested to add the Script of Hanya (also in CC) to the
> Open Office Release as a first improvement.
> On the discussion in this thread @dev declared only stuff that is in
> trunc can be part of an release.
> Since Hanya has comitter rights granted it was suggested he should be
> the one commiting his script.
>
> @Hanya: Do you believe that your script is stable enough to be added
> or is there work to do to get it commited?
> Can you commit your work, so we can add it for release?
>
> @Jim (Release Manager):
> What is the timeframe for you to get this script into 4.1.4. You only
> stated that it has to be in svn, not until when and what the timeframe
> is. My understanding is the current Version is close to a RC.
>
> Hope this drives this topic a little further.
>
> All the best
> Peter
>
> Am 13.06.2017 um 23:42 schrieb Marcus:
>> Am 13.06.2017 um 23:24 schrieb Andrea Pescetti:
>>> Marcus wrote:
>>>> assumed it's OK on trunk and 4.1.4, how do we integrate this into the
>>>> installation process?
>>>
>>> I see it as an on-demand tool. So nothing would be added to the
>>> installation process. A new menu item would be available for it (the
>>> current solution uses the macro runner menu).
>>>
>>> It seems, though, that the current implementation relies on being
>>> executed from the user profile and this will probably not work for
>>> our 4.1.4 use case: I haven't checked, but I believe that the
>>> profile is left unchanged by maintenance (4.1.x) updates. This
>>> should be investigated though: there is likely a way to bundle it as
>>> a "shared" script that would then be available even without touching
>>> the profile.
>>
>> an alternative would be to create a new Help menu entry (e.g., "Help
>> - Spell check fix"). This opens a webpage which provides a download
>> link to the file and a text with explainations/instructions: Why is
>> it needed, how to unpack/install/execute it, what is it going to do,
>> etc.
>>
>> Marcus
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]

Loading...