tauruslib-devel — taurus development mailing list

Re: [tauruslib-devel] [Tango-info] Taurus Follow up meeting

[Emilio J. M. A. <emo...@ce...>]

Hello,

This email is to remind you of this afternoon's appointmentfrom 15h00 to 
16h00 (UTC +2) .

You can find the zoom link [1] and agenda [2] below.


Kind regards

[1] 
https://rediris.zoom.us/j/87684922859?pwd=a09MNlpJY0NrYUQ0UnJaakk4QzQ3QT09
[2] 
https://gitlab.com/taurus-org/taurus-followup/-/blob/main/next_meeting/AGENDA.md

On 21/7/23 10:04, Guifré Cuní wrote:
> Dear Community,
>
> We are glad to announce the first "Taurus Follow up meeting".
> Details are listed below:
>
> * Date: 09.Aug.2023
> * Hour: from 15h00 to 16h00 (UTC +2)
> * Place: Remote, Zoom meeting [1]
> * Agenda: You can find the proposed agenda at [2]
>
> Please save the date in your calendar and in case you have comments, 
> suggestions or doubts you can contact us at: zre...@ce..., 
> mc...@ce... and emo...@ce....
>
> Hope to see you there!
>
>
> Cheers,
> Guifré Cuní on behalf of the Controls Section of the ALBA Synchrotron
>
> [1] 
> https://rediris.zoom.us/j/87684922859?pwd=a09MNlpJY0NrYUQ0UnJaakk4QzQ3QT09
> [2] 
> https://gitlab.com/taurus-org/taurus-followup/-/blob/main/next_meeting/AGENDA.md
>
> To unsubscribe from this mailing list send an email to...@li...  with the subject set to "unsubscribe info".
-- 


-- 

Un saludo


ALBA Synchrotron <http://www.albasynchrotron.es>

	Emilio Morales
Controls Section - Computing Division

ALBA SYNCHROTRON LIGHT SOURCE
<http://www.cells.es/en/about/coming-to-alba>Carrer de la Llum 2-26 | 
08290 | Cerdanyola del Vallès| Barcelona | Spain 
<http://www.cells.es/en/about/coming-to-alba>
(+34) 93 592 40 89 - (+34) 618 31 53 75
www.albasynchrotron.es <http://www.albasynchrotron.es>| emo...@ce...

**Please, do not print this e-mail unless it is absolutely necessary.
**Si heu rebut aquest correu per error, us informo que pot contenir 
informació confidencial i privada i que està prohibit el seu ús. Us 
agrairíem que ho comuniqueu al remitent i l'elimineu. Gràcies.
Si ha recibido este correo por error, le informo de que puede contener 
información confidencial y privada y que está prohibido su uso. Le 
agradeceré que lo comunique a su remitente y lo elimine. Gracias.
If you have received this e-mail in error, please note that it may 
contain confidential and private information, therefore, the use of this 
information is strictly forbidden. Please inform the sender of the error 
and delete the information received. Thank you.

[tauruslib-devel] Taurus Follow up meeting

[Guifré C. <gui...@ce...>]

Dear Community,

We are glad to announce the first "Taurus Follow up meeting".
Details are listed below:

* Date: 09.Aug.2023
* Hour: from 15h00 to 16h00 (UTC +2)
* Place: Remote, Zoom meeting [1]
* Agenda: You can find the proposed agenda at [2]

Please save the date in your calendar and in case you have comments, 
suggestions or doubts you can contact us at: zre...@ce..., 
mc...@ce... and emo...@ce....

Hope to see you there!


Cheers,
Guifré Cuní on behalf of the Controls Section of the ALBA Synchrotron

[1] 
https://rediris.zoom.us/j/87684922859?pwd=a09MNlpJY0NrYUQ0UnJaakk4QzQ3QT09
[2] 
https://gitlab.com/taurus-org/taurus-followup/-/blob/main/next_meeting/AGENDA.md

Re: [tauruslib-devel] Taurus project first follow-up meeting - invitation & poll

[Guifré C. <gui...@ce...>]

Dear Community,

after some feedback during the TANGO Meeting, we update the poll with 
some options in August:


We will really appreciate if you update your input at:
https://framadate.org/emnyoVynZdVSoPna


Thanks,
Guifré.


On 23/6/23 12:49, Guifré Cuní wrote:
> Dear Community,
>
> We are thrilled to announce the first follow-up meeting for the Taurus 
> project, which aims to enhance the Taurus Community and build upon the 
> decisions made during the Tango SIG - Taurus Workshop [1]. We 
> cordially invite you to join us for this important gathering.
>
> To ensure that we accommodate everyone's availability, we kindly 
> request you to participate in the availability poll [2]. The poll will 
> remain open until the end of June, after which we will finalize the 
> meeting date.
>
> For your reference, the tentative agenda can be found here [3].
>
> We look forward to your active participation and valuable contributions.
>
>
> Best regards,
>
> Guifré Cuní on behalf of the Controls Section of the ALBA Synchrotron
>
> [1] Tango SIG - Taurus Workshop Indico: https://indico.esrf.fr/event/76
> [2] Availability poll: https://framadate.org/emnyoVynZdVSoPna
> [3] Tentative agenda: 
> https://gitlab.com/taurus-org/taurus-followup/-/blob/main/next_meeting/AGENDA.md 
>

[tauruslib-devel] Taurus project first follow-up meeting - invitation & poll

[Guifré C. <gui...@ce...>]

Dear Community,

We are thrilled to announce the first follow-up meeting for the Taurus 
project, which aims to enhance the Taurus Community and build upon the 
decisions made during the Tango SIG - Taurus Workshop [1]. We cordially 
invite you to join us for this important gathering.

To ensure that we accommodate everyone's availability, we kindly request 
you to participate in the availability poll [2]. The poll will remain 
open until the end of June, after which we will finalize the meeting date.

For your reference, the tentative agenda can be found here [3].

We look forward to your active participation and valuable contributions.


Best regards,

Guifré Cuní on behalf of the Controls Section of the ALBA Synchrotron

[1] Tango SIG - Taurus Workshop Indico: https://indico.esrf.fr/event/76
[2] Availability poll: https://framadate.org/emnyoVynZdVSoPna
[3] Tentative agenda: 
https://gitlab.com/taurus-org/taurus-followup/-/blob/main/next_meeting/AGENDA.md 

[tauruslib-devel] TAURUS workshop postponed to March 14th & 15th 2023.

[Nicolas L. <nic...@es...>]

Dear all,

Our TAURUS workshop is finally postponed to March 14th & 15th 2023.

Please be sure to register on our Indico website <https://indico.esrf.fr/event/76/> so that you will receive the connection information (zoom link and access code). 

This website is also the right place to submit your contributions. 

Kind regards, 
The organizing committee. 

Re: [tauruslib-devel] Taurus workshop on "Feedback and plans for the future"

[Guifré C. <gui...@ce...>]

Deal all,

The French unions are planning a major strike on March 7th 2023, the 
first day of the TAURUS meeting, which could paralyze the country.

For the moment, we don’t know whether this will be a one-day action.

Should the strike be maintained in the following days, it will be highly 
difficult for those attending the workshop in person to travel home due 
to the disruption of transportation services.

Regarding the organization of our workshop, we have two options:

 1. we maintain the initial dates, but switch to a pure remote event (1),
 2. we postpone it to March 14th & 15th, while still keeping the hybrid
    mode – with the hope that the strike will be over.

As the organizer of this event, the ESRF would be pleased to welcome you 
on site, but we understand that this could be an unacceptable change in 
your calendar.

We consequently suggest that we fill a framaform 
<https://framaforms.org/taurus-workshop-keep-initial-dates-or-postpone-the-event-1676295395> (2) 
so that we can reach a conclusion on the option to select.

We apologize for the inconvenience caused.

Kind regards,

Zbigniew Reszela & Guifré Cuní - ALBA

Nicolas Leclercq - ESRF

(1) we can still welcome you on site, in case you wish to attend in 
person despite the situation.

(2) 
https://framaforms.org/taurus-workshop-keep-initial-dates-or-postpone-the-event-1676295395



On 27/1/23 11:35, Guifré Cuní wrote:
>
> Dear all,
>
> The last 9 months of Taurus lifetime was a period of minimal activity. 
> The lastremarkable event was the Taurus webinar [1], at the same time, 
> a farewell of the main project maintainer.
>
> Now, the TANGO Community, with an initiative of the ESRF, is 
> organizing a Taurus workshop on March 7th & 8th 2023. The aim of this 
> meeting is twofold to:
>
>   * share the GUI strategy for the future of the institutes using Taurus
>   * discuss on the organizational and technical future of Taurus itself.
>
> The workshop will be organized in hybrid mode. We would like to kindly 
> invite you in participating in it, as speakers and attendees. You will 
> find all the necessary information about this event on this Indico 
> page [2].
>
>
> Best regards,
>
> Zbigniew Reszela & Guifré Cuní - ALBA
>
> Nicolas Leclercq - ESRF
>
>
> [1] 
> https://gitlab.com/taurus-org/taurus/-/wikis/Taurus-webinar-(for-maintainers)
>
> [2] https://indico.esrf.fr/event/76/
>
>
>
> _______________________________________________
> Tauruslib-devel mailing list
> Tau...@li...
> https://lists.sourceforge.net/lists/listinfo/tauruslib-devel

Re: [tauruslib-devel] Taurus workshop on "Feedback and plans for the future"

[Guifré C. <gui...@ce...>]

Deal all,

The French unions are planning a major strike on March 7th 2023, the 
first day of the TAURUS meeting, which could paralyze the country.

For the moment, we don’t know whether this will be a one-day action.

Should the strike be maintained in the following days, it will be highly 
difficult for those attending the workshop in person to travel home due 
to the disruption of transportation services.

Regarding the organization of our workshop, we have two options:

 1. we maintain the initial dates, but switch to a pure remote event (1),
 2. we postpone it to March 14th & 15th, while still keeping the hybrid
    mode – with the hope that the strike will be over.

As the organizer of this event, the ESRF would be pleased to welcome you 
on site, but we understand that this could be an unacceptable change in 
your calendar.

We consequently suggest that we fill a framaform 
<https://framaforms.org/taurus-workshop-keep-initial-dates-or-postpone-the-event-1676295395> (2) 
so that we can reach a conclusion on the option to select.

We apologize for the inconvenience caused.

Kind regards,

Zbigniew Reszela & Guifré Cuní - ALBA

Nicolas Leclercq - ESRF

(1) we can still welcome you on site, in case you wish to attend in 
person despite the situation.

(2) 
https://framaforms.org/taurus-workshop-keep-initial-dates-or-postpone-the-event-1676295395



On 27/1/23 11:35, Guifré Cuní wrote:
>
> Dear all,
>
> The last 9 months of Taurus lifetime was a period of minimal activity. 
> The lastremarkable event was the Taurus webinar [1], at the same time, 
> a farewell of the main project maintainer.
>
> Now, the TANGO Community, with an initiative of the ESRF, is 
> organizing a Taurus workshop on March 7th & 8th 2023. The aim of this 
> meeting is twofold to:
>
>   * share the GUI strategy for the future of the institutes using Taurus
>   * discuss on the organizational and technical future of Taurus itself.
>
> The workshop will be organized in hybrid mode. We would like to kindly 
> invite you in participating in it, as speakers and attendees. You will 
> find all the necessary information about this event on this Indico 
> page [2].
>
>
> Best regards,
>
> Zbigniew Reszela & Guifré Cuní - ALBA
>
> Nicolas Leclercq - ESRF
>
>
> [1] 
> https://gitlab.com/taurus-org/taurus/-/wikis/Taurus-webinar-(for-maintainers)
>
> [2] https://indico.esrf.fr/event/76/
>

[tauruslib-devel] Taurus workshop on "Feedback and plans for the future"

[Guifré C. <gui...@ce...>]

Dear all,

The last 9 months of Taurus lifetime was a period of minimal activity. 
The lastremarkable event was the Taurus webinar [1], at the same time, a 
farewell of the main project maintainer.

Now, the TANGO Community, with an initiative of the ESRF, is organizing 
a Taurus workshop on March 7th & 8th 2023. The aim of this meeting is 
twofold to:

  * share the GUI strategy for the future of the institutes using Taurus
  * discuss on the organizational and technical future of Taurus itself.

The workshop will be organized in hybrid mode. We would like to kindly 
invite you in participating in it, as speakers and attendees. You will 
find all the necessary information about this event on this Indico page 
[2].


Best regards,

Zbigniew Reszela & Guifré Cuní - ALBA

Nicolas Leclercq - ESRF


[1] 
https://gitlab.com/taurus-org/taurus/-/wikis/Taurus-webinar-(for-maintainers)

[2] https://indico.esrf.fr/event/76/

[tauruslib-devel] Taurus Webinar videos

[Reynald B. <rey...@es...>]

Dear all,

The videos of the Taurus Tango Kernel Webinar are available 
ontango-controls youtube channel 
<https://www.youtube.com/channel/UCezS9cMkektZNItYnPOAQvg>:

  * Part 1: https://youtu.be/wmpBqxzqGV4 <https://youtu.be/wmpBqxzqGV4>
  * Bonus during break: https://youtu.be/G20oAeOih2k
    <https://youtu.be/G20oAeOih2k>
  * Part 2: https://youtu.be/vhjsXphJ_o4 <https://youtu.be/vhjsXphJ_o4>

Enjoy!

Reynald

PS: Many thanks Carlos for this webinar and for all the amazing work 
you've done for the Taurus and Tango community! All the best in your new 
life!

Re: [tauruslib-devel] [Tango-info] Farewell and Taurus Webinar (Zoom link)

[Carlos Pascual-I. <cpa...@ce...>]

Reminder:

On 21/04/2022 18:45, Carlos Pascual-Izarra wrote:
> Hi all,
>
> Here is the link for the taurus webinar (thanks Reynald for organising!):
>
> Topic: Taurus Webinar
> Time: Apr 27, 2022 09:30 AM Paris
>
> Join Zoom Meeting
> https://esrf.zoom.us/j/94720236609?pwd=ZGVCQVk4eGFzZi9yZDhSQTV4ckc2UT09
>
> Meeting ID: 947 2023 6609
> Passcode: 461099
> One tap mobile
> +33170379729,,94720236609#,,,,*461099# France
> +33170950103,,94720236609#,,,,*461099# France
>
> Dial by your location
>         +33 1 7037 9729 France
>         +33 1 7095 0103 France
>         +33 1 7095 0350 France
>         +33 1 8699 5831 France
>         +33 1 7037 2246 France
> Meeting ID: 947 2023 6609
> Passcode: 461099
> Find your local number: https://esrf.zoom.us/u/abPFBjOcr8
>
>
>
> To unsubscribe from this mailing list send an email to sy...@li... with the subject set to "unsubscribe info".

-- 
+----------------------------------------------------+
  Carlos Pascual Izarra
  Scientific Software Coordinator
  Computing Division
  ALBA Synchrotron  [http://www.albasynchrotron.es]
  Carrer de la Llum 2-26
  E-08290 Cerdanyola del Valles (Barcelona), Spain
  E-mail: cpa...@ce...
  Phone: +34 93 592 4428
+----------------------------------------------------+

Re: [tauruslib-devel] Farewell and Taurus Webinar (Zoom link)

[Carlos Pascual-I. <cpa...@ce...>]

Hi all,

Here is the link for the taurus webinar (thanks Reynald for organising!):

Topic: Taurus Webinar
Time: Apr 27, 2022 09:30 AM Paris

Join Zoom Meeting
https://esrf.zoom.us/j/94720236609?pwd=ZGVCQVk4eGFzZi9yZDhSQTV4ckc2UT09

Meeting ID: 947 2023 6609
Passcode: 461099
One tap mobile
+33170379729,,94720236609#,,,,*461099# France
+33170950103,,94720236609#,,,,*461099# France

Dial by your location
         +33 1 7037 9729 France
         +33 1 7095 0103 France
         +33 1 7095 0350 France
         +33 1 8699 5831 France
         +33 1 7037 2246 France
Meeting ID: 947 2023 6609
Passcode: 461099
Find your local number: https://esrf.zoom.us/u/abPFBjOcr8


-- 
+----------------------------------------------------+
  Carlos Pascual Izarra
  Scientific Software Coordinator
  Computing Division
  ALBA Synchrotron  [http://www.albasynchrotron.es]
  Carrer de la Llum 2-26
  E-08290 Cerdanyola del Valles (Barcelona), Spain
  E-mail: cpa...@ce...
  Phone: +34 93 592 4428
+----------------------------------------------------+

Re: [tauruslib-devel] FW: [Tango-info] Farewell and Taurus Webinar

[Carlos Pascual-I. <cpa...@ce...>]

Ups! sorry...

In my euro-centrism I forgot to specify the timezone for the seminar. 
The start is 9:30 CEST (i.e. UTC+2)

Thanks Sonja for pointing it out!

Regarding the link for the webinar, I'll pass it as soon as I have it.

Cheers!

Carlos

On 19/04/2022 15:25, Vrcic, Sonja wrote:
>
> Hello Carlos,
>
> Thank you for the invitation to the webinar.   The invite does not 
> specify the time zone,  is this scheduled to start at 09:30 UTC+2  ?
>
> Thank you,
>
> Sonja
>
> *From: *<inf...@ta...> on behalf of Carlos 
> Pascual-Izarra <cpa...@ce...>
> *Reply to: *Carlos Pascual-Izarra <cpa...@ce...>
> *Date: *Tuesday, 19 April 2022 at 12:14
> *To: *"tau...@li..." 
> <tau...@li...>, "in...@ta..." 
> <in...@ta...>
> *Subject: *Re: [Tango-info] [tauruslib-devel] Farewell and Taurus Webinar
>
> Hi,
>
> This is an update to confirm that the taurus webinar is planned for 
> Wednesday, 27th of April at 9:30am (expecting to extend till 13:00).
>
> A work-in-progress draft of the notes for the webinar can be found in 
> the taurus wiki:
>
> https://gitlab.com/taurus-org/taurus/-/wikis/Taurus-webinar-(for-maintainers)
>
> Carlos
>
> On 4/4/22 16:25, Carlos Pascual-Izarra wrote:
>
>     Hi all,
>
>     As some of you may know, I’ve been the main maintainer of Taurus
>     (as well as an occasional contributor to other projects within the
>     Tango community) for a long time.
>
>     Now I am taking one step in my professional career and leaving
>     ALBA’s Controls group, which unfortunately implies detaching from
>     the Taurus project and the Tango community.
>
>     But before leaving, I’ve been kindly asked to organize a
>     knowledge-transfer webinar to facilitate other people taking over
>     with Taurus maintenance.
>
>     The tentative date for the webinar is 27th of April.
>
>     The idea is *not* to do an exhaustive review of Taurus for new
>     users, but rather to focus on specific aspects that may be of more
>     value to current Taurus users/developers who may consider getting
>     more involved in the Taurus maintenance and development.
>
>     I hope to see some of you there!
>
>     Carlos
>
>     PS: Below is a draft for the contents of the webinar. *Suggestions
>     for removal/inclusion of topics are most welcome*
>
>     Contents:
>
>       * taurus-org <https://gitlab.com/taurus-org> and related
>         repositories
>       * Sources of docs
>
>           o official docs <http://taurus-scada.org/>
>           o wiki <https://gitlab.com/taurus-org/taurus/-/wikis/home>
>           o Taurus4 best practices
>             <https://gitlab.com/taurus-org/taurus/-/wikis/Best-Practices-for-Taurus-4>
>
>           o ESO ELT Control user UI Tutorial
>             <https://www.eso.org/~ahoffsta/docs/v1.2.0/introduction/html/docs/introduction.html#python>
>
>
>       * Workflows for contributing to Taurus (issues, MRs, TEPs,…)
>       * Taurus plugins (and entry points in Taurus). TEP13
>         <http://www.taurus-scada.org/tep?TEP13.md>
>       * Structure of Taurus project and official API of taurus
>         <https://www.taurus-scada.org/devel/api/index.html>
>       * CLI
>
>           o current taurus subcommands
>           o click
>           o taurus subcommands entry-point
>
>       * User and system settings (new!)
>       * Quick review of generic widgets catalog
>
>           o display, input, button, panel, table, tree container,…
>           o plotting in Taurus (taurus-pyqtgraph and guiqwt)
>           o synoptics: built-in (jdraw) vs svgsynoptic plugin
>
>       * The various levels of GUI development in Taurus
>
>           o using TaurusGui
>           o using the designer (dynamic .ui loading!)
>           o programmatic
>
>       * Forms:
>
>           o TaurusValue and factories
>
>       * Taurus core
>
>           o taurus models (auth, device, attr) and validators
>           o how to create a new scheme
>           o pint units integration (the less-understood feature in
>             taurus!)
>           o advanced uses of the evaluation scheme
>           o Tango events/polling…
>
>               + issue with Tango attr timeouts
>               + issue with slow GUI start times (Tango event
>                 subscription)
>               + new tango scheme
>                 <https://gitlab.com/taurus-org/tg_scheme>
>
>       * Developing new Taurus widgets
>
>           o |TaurusBaseComponent|: event handling, thread decoupling,
>             filtering, …
>           o |TaurusBaseConfigurableClass|: config properties / config
>             delegates
>           o scheme agnosticism
>             <https://gitlab.com/taurus-org/taurus/-/wikis/Best-Practices-for-Taurus-4#scheme-agnosticism-avoid-tango-centric-code>
>
>           o codecs API
>           o formatters API
>           o multi-model API (new!)
>
>       * Supported Qt bindings and |taurus.external.qt|
>       * TaurusGUI customization mess: .py vs .xml vs .ini files
>       * Test and CI
>
>           o gitlab-ci
>           o supported python versions
>           o precommit, flake8 and black
>           o docker images
>           o vagrant
>
>       * Releases and packaging
>
>           o release schedule and manual tests
>           o pypi
>
>           o conda: conda-forge and deprecated conda channels
>           o official debian packaging repositories for taurus
>             <https://salsa.debian.org/science-team/taurus/> and
>             taurus-pyqtgraph
>             <https://salsa.debian.org/science-team/taurus-pyqtgraph>
>           o unnofficial debian repositories and backports (ALBA)
>
>       * Ideas for future directions
>
>           o relaxing release schedule and doing continuous delivery
>
>           o provide public debian repo with latest backports
>           o decoupling of tango-centric code as a plugin
>           o make use of the multi-model API for e.g. Taurus Labels
>           o improving the tangoarchiving scheme
>           o polishing taurus-pyqtgraph
>           o replacing guiqwt with pyqtgraph for 2D and 3D plots
>           o make use of units API in widgets (e.g. selectable units in
>             taurus forms)
>           o improving svgsynoptics
>           o improve enum support (get rid of custom enumeration class
>             in taurus)
>           o …
>
>       * Open Questions
>
>     -- 
>
>     +----------------------------------------------------+
>
>       Carlos Pascual Izarra
>
>       Scientific Software Coordinator
>
>       Computing Division
>
>       ALBA Synchrotron  [http://www.albasynchrotron.es]
>
>       Carrer de la Llum 2-26
>
>       E-08290 Cerdanyola del Valles (Barcelona), Spain
>
>       E-mail:cpa...@ce...
>
>       Phone: +34 93 592 4428
>
>     +----------------------------------------------------+
>
>
>
>
>     _______________________________________________
>
>     Tauruslib-devel mailing list
>
>     Tau...@li...
>
>     https://lists.sourceforge.net/lists/listinfo/tauruslib-devel
>
> -- 
> +----------------------------------------------------+
>   Carlos Pascual Izarra
>   Scientific Software Coordinator
>   Computing Division
>   ALBA Synchrotron  [http://www.albasynchrotron.es]
>   Carrer de la Llum 2-26
>   E-08290 Cerdanyola del Valles (Barcelona), Spain
>   E-mail:cpa...@ce...
>   Phone: +34 93 592 4428
> +----------------------------------------------------+
>
>
> The SKA Observatory is an inter-governmental organisation and the 
> successor of SKA Organisation, a private limited company by guarantee 
> registered in England and Wales with registered number 07881918, with 
> a registered office of Jodrell Bank, Lower Withington, Macclesfield, 
> Cheshire, England, SK11 9FT.
>
> This message is intended solely for the addressee and may contain 
> confidential information. If you have received this message in error, 
> please inform the sender, and immediately and permanently delete the 
> email. Do not use, copy or disclose the information contained in this 
> message or in any attachment.
>
> This email has been scanned for viruses and malware, and may have been 
> automatically archived, by Mimecast Ltd. Although SKA Observatory and 
> SKA Organisation have taken reasonable precautions to ensure no 
> viruses are present in this email, neither SKA Observatory nor SKA 
> Organisation accept responsibility for any loss or damage sustained as 
> a result of computer viruses and the recipient must ensure that the 
> email (and attachments) are virus free. 

-- 
+----------------------------------------------------+
  Carlos Pascual Izarra
  Scientific Software Coordinator
  Computing Division
  ALBA Synchrotron  [http://www.albasynchrotron.es]
  Carrer de la Llum 2-26
  E-08290 Cerdanyola del Valles (Barcelona), Spain
  E-mail:cpa...@ce...
  Phone: +34 93 592 4428
+----------------------------------------------------+

Re: [tauruslib-devel] Farewell and Taurus Webinar

[Carlos Pascual-I. <cpa...@ce...>]

Hi,

This is an update to confirm that the taurus webinar is planned for 
Wednesday, 27th of April at 9:30am (expecting to extend till 13:00).

A work-in-progress draft of the notes for the webinar can be found in 
the taurus wiki:

https://gitlab.com/taurus-org/taurus/-/wikis/Taurus-webinar-(for-maintainers)

Carlos


On 4/4/22 16:25, Carlos Pascual-Izarra wrote:
>
> Hi all,
>
> As some of you may know, I’ve been the main maintainer of Taurus (as 
> well as an occasional contributor to other projects within the Tango 
> community) for a long time.
>
> Now I am taking one step in my professional career and leaving ALBA’s 
> Controls group, which unfortunately implies detaching from the Taurus 
> project and the Tango community.
>
> But before leaving, I’ve been kindly asked to organize a 
> knowledge-transfer webinar to facilitate other people taking over with 
> Taurus maintenance.
>
> The tentative date for the webinar is 27th of April.
>
> The idea is *not*to do an exhaustive review of Taurus for new users, 
> but rather to focus on specific aspects that may be of more value to 
> current Taurus users/developers who may consider getting more involved 
> in the Taurus maintenance and development.
>
> I hope to see some of you there!
>
> Carlos
>
> PS: Below is a draft for the contents of the webinar. *Suggestions for 
> removal/inclusion of topics are most welcome*
>
> Contents:
>
>   * taurus-org <https://gitlab.com/taurus-org>and related repositories
>   * Sources of docs
>       o official docs <http://taurus-scada.org/>
>       o wiki <https://gitlab.com/taurus-org/taurus/-/wikis/home>
>       o Taurus4 best practices
>         <https://gitlab.com/taurus-org/taurus/-/wikis/Best-Practices-for-Taurus-4>
>       o ESO ELT Control user UI Tutorial
>         <https://www.eso.org/~ahoffsta/docs/v1.2.0/introduction/html/docs/introduction.html#python>
>   * Workflows for contributing to Taurus (issues, MRs, TEPs,…)
>   * Taurus plugins (and entry points in Taurus). TEP13
>     <http://www.taurus-scada.org/tep?TEP13.md>
>   * Structure of Taurus project and official API of taurus
>     <https://www.taurus-scada.org/devel/api/index.html>
>   * CLI
>       o current taurus subcommands
>       o click
>       o taurus subcommands entry-point
>   * User and system settings (new!)
>   * Quick review of generic widgets catalog
>       o display, input, button, panel, table, tree container,…
>       o plotting in Taurus (taurus-pyqtgraph and guiqwt)
>       o synoptics: built-in (jdraw) vs svgsynoptic plugin
>   * The various levels of GUI development in Taurus
>       o using TaurusGui
>       o using the designer (dynamic .ui loading!)
>       o programmatic
>   * Forms:
>       o TaurusValue and factories
>   * Taurus core
>       o taurus models (auth, device, attr) and validators
>       o how to create a new scheme
>       o pint units integration (the less-understood feature in taurus!)
>       o advanced uses of the evaluation scheme
>       o Tango events/polling…
>           + issue with Tango attr timeouts
>           + issue with slow GUI start times (Tango event subscription)
>           + new tango scheme <https://gitlab.com/taurus-org/tg_scheme>
>   * Developing new Taurus widgets
>       o |TaurusBaseComponent|: event handling, thread decoupling,
>         filtering, …
>       o |TaurusBaseConfigurableClass|: config properties / config
>         delegates
>       o scheme agnosticism
>         <https://gitlab.com/taurus-org/taurus/-/wikis/Best-Practices-for-Taurus-4#scheme-agnosticism-avoid-tango-centric-code>
>       o codecs API
>       o formatters API
>       o multi-model API (new!)
>   * Supported Qt bindings and |taurus.external.qt|
>   * TaurusGUI customization mess: .py vs .xml vs .ini files
>   * Test and CI
>       o gitlab-ci
>       o supported python versions
>       o precommit, flake8 and black
>       o docker images
>       o vagrant
>   * Releases and packaging
>       o release schedule and manual tests
>       o pypi
>       o conda: conda-forge and deprecated conda channels
>       o official debian packaging repositories for taurus
>         <https://salsa.debian.org/science-team/taurus/>and
>         taurus-pyqtgraph
>         <https://salsa.debian.org/science-team/taurus-pyqtgraph>
>       o unnofficial debian repositories and backports (ALBA)
>   * Ideas for future directions
>       o relaxing release schedule and doing continuous delivery
>       o provide public debian repo with latest backports
>       o decoupling of tango-centric code as a plugin
>       o make use of the multi-model API for e.g. Taurus Labels
>       o improving the tangoarchiving scheme
>       o polishing taurus-pyqtgraph
>       o replacing guiqwt with pyqtgraph for 2D and 3D plots
>       o make use of units API in widgets (e.g. selectable units in
>         taurus forms)
>       o improving svgsynoptics
>       o improve enum support (get rid of custom enumeration class in
>         taurus)
>       o …
>   * Open Questions
>
> -- 
> +----------------------------------------------------+
>   Carlos Pascual Izarra
>   Scientific Software Coordinator
>   Computing Division
>   ALBA Synchrotron  [http://www.albasynchrotron.es]
>   Carrer de la Llum 2-26
>   E-08290 Cerdanyola del Valles (Barcelona), Spain
>   E-mail:cpa...@ce...
>   Phone: +34 93 592 4428
> +----------------------------------------------------+
>
>
> _______________________________________________
> Tauruslib-devel mailing list
> Tau...@li...
> https://lists.sourceforge.net/lists/listinfo/tauruslib-devel

-- 
+----------------------------------------------------+
  Carlos Pascual Izarra
  Scientific Software Coordinator
  Computing Division
  ALBA Synchrotron  [http://www.albasynchrotron.es]
  Carrer de la Llum 2-26
  E-08290 Cerdanyola del Valles (Barcelona), Spain
  E-mail:cpa...@ce...
  Phone: +34 93 592 4428
+----------------------------------------------------+

[tauruslib-devel] (unnofficial) taurus 5.1.4 release

[Carlos Pascual-I. <cpa...@ce...>]

Hi all

This is just to inform that I did an "unofficial" release of taurus 
(5.1.4) in order to

tidy-up things for those who take over the maintenance of the project.

Basically, I tagged the current develop HEAD as 5.1.4 but I did not 
merge into stable.

Essentially this brings the TEP20 and should be safe to use, but it did 
not go

through the whole manual tests we usually do in official releases.


See more details in the CHANGELOG:

https://gitlab.com/taurus-org/taurus/-/blob/develop/CHANGELOG.md

Cheers,


Carlos

-- 
+----------------------------------------------------+
  Carlos Pascual Izarra
  Scientific Software Coordinator
  Computing Division
  ALBA Synchrotron  [http://www.albasynchrotron.es]
  Carrer de la Llum 2-26
  E-08290 Cerdanyola del Valles (Barcelona), Spain
  E-mail: cpa...@ce...
  Phone: +34 93 592 4428
+----------------------------------------------------+

[tauruslib-devel] Farewell and Taurus Webinar

[Carlos Pascual-I. <cpa...@ce...>]

Hi all,

As some of you may know, I’ve been the main maintainer of Taurus (as 
well as an occasional contributor to other projects within the Tango 
community) for a long time.

Now I am taking one step in my professional career and leaving ALBA’s 
Controls group, which unfortunately implies detaching from the Taurus 
project and the Tango community.

But before leaving, I’ve been kindly asked to organize a 
knowledge-transfer webinar to facilitate other people taking over with 
Taurus maintenance.

The tentative date for the webinar is 27th of April.

The idea is *not*to do an exhaustive review of Taurus for new users, but 
rather to focus on specific aspects that may be of more value to current 
Taurus users/developers who may consider getting more involved in the 
Taurus maintenance and development.

I hope to see some of you there!

Carlos

PS: Below is a draft for the contents of the webinar. *Suggestions for 
removal/inclusion of topics are most welcome*

Contents:

  * taurus-org <https://gitlab.com/taurus-org>and related repositories
  * Sources of docs
      o official docs <http://taurus-scada.org/>
      o wiki <https://gitlab.com/taurus-org/taurus/-/wikis/home>
      o Taurus4 best practices
        <https://gitlab.com/taurus-org/taurus/-/wikis/Best-Practices-for-Taurus-4>
      o ESO ELT Control user UI Tutorial
        <https://www.eso.org/~ahoffsta/docs/v1.2.0/introduction/html/docs/introduction.html#python>
  * Workflows for contributing to Taurus (issues, MRs, TEPs,…)
  * Taurus plugins (and entry points in Taurus). TEP13
    <http://www.taurus-scada.org/tep?TEP13.md>
  * Structure of Taurus project and official API of taurus
    <https://www.taurus-scada.org/devel/api/index.html>
  * CLI
      o current taurus subcommands
      o click
      o taurus subcommands entry-point
  * User and system settings (new!)
  * Quick review of generic widgets catalog
      o display, input, button, panel, table, tree container,…
      o plotting in Taurus (taurus-pyqtgraph and guiqwt)
      o synoptics: built-in (jdraw) vs svgsynoptic plugin
  * The various levels of GUI development in Taurus
      o using TaurusGui
      o using the designer (dynamic .ui loading!)
      o programmatic
  * Forms:
      o TaurusValue and factories
  * Taurus core
      o taurus models (auth, device, attr) and validators
      o how to create a new scheme
      o pint units integration (the less-understood feature in taurus!)
      o advanced uses of the evaluation scheme
      o Tango events/polling…
          + issue with Tango attr timeouts
          + issue with slow GUI start times (Tango event subscription)
          + new tango scheme <https://gitlab.com/taurus-org/tg_scheme>
  * Developing new Taurus widgets
      o |TaurusBaseComponent|: event handling, thread decoupling,
        filtering, …
      o |TaurusBaseConfigurableClass|: config properties / config delegates
      o scheme agnosticism
        <https://gitlab.com/taurus-org/taurus/-/wikis/Best-Practices-for-Taurus-4#scheme-agnosticism-avoid-tango-centric-code>
      o codecs API
      o formatters API
      o multi-model API (new!)
  * Supported Qt bindings and |taurus.external.qt|
  * TaurusGUI customization mess: .py vs .xml vs .ini files
  * Test and CI
      o gitlab-ci
      o supported python versions
      o precommit, flake8 and black
      o docker images
      o vagrant
  * Releases and packaging
      o release schedule and manual tests
      o pypi
      o conda: conda-forge and deprecated conda channels
      o official debian packaging repositories for taurus
        <https://salsa.debian.org/science-team/taurus/>and
        taurus-pyqtgraph
        <https://salsa.debian.org/science-team/taurus-pyqtgraph>
      o unnofficial debian repositories and backports (ALBA)
  * Ideas for future directions
      o relaxing release schedule and doing continuous delivery
      o provide public debian repo with latest backports
      o decoupling of tango-centric code as a plugin
      o make use of the multi-model API for e.g. Taurus Labels
      o improving the tangoarchiving scheme
      o polishing taurus-pyqtgraph
      o replacing guiqwt with pyqtgraph for 2D and 3D plots
      o make use of units API in widgets (e.g. selectable units in
        taurus forms)
      o improving svgsynoptics
      o improve enum support (get rid of custom enumeration class in taurus)
      o …
  * Open Questions

-- 
+----------------------------------------------------+
  Carlos Pascual Izarra
  Scientific Software Coordinator
  Computing Division
  ALBA Synchrotron  [http://www.albasynchrotron.es]
  Carrer de la Llum 2-26
  E-08290 Cerdanyola del Valles (Barcelona), Spain
  E-mail:cpa...@ce...
  Phone: +34 93 592 4428
+----------------------------------------------------+

[tauruslib-devel] New release of Taurus 5.0.0 (Jul21)

[Carlos Pascual-I. <cpa...@ce...>]

We are happy to announce the release of Taurus 5.0.0.

This is a major release that removes support of Python2 and Qt4 (we now 
support python >= 3.5 and the PyQt5 and PySide2 bindings). Other than 
that there should not be any other backwards incompatibility between 5.x 
and 4.x (we intentionally avoided enforcing the pending deprecations of 
4.x even if this is a major version bump) so:

**if something works on taurus 4.8 using python3 and Qt5 and it does not 
work in taurus 5, please report it as a bug**

Note for developers: the API documentation has been improved: classes 
and other members which are not "public" are no longer included in the 
API docs while all public members should now be included.

This release also improves the module loading times in some situations, 
and it provides a long-awaited feature: installation-independent config 
files (no more need of editing tauruscustomsettings.py)


The source files can be downloaded from:

     https://pypi.org/project/taurus/5.0.0/

The documentation (including installation instructions for different 
platforms) is available at:

     http://www.taurus-scada.org

For a detailed list of changes, see the CHANGELOG:

https://gitlab.com/taurus-org/taurus/-/blob/develop/CHANGELOG.md

If you encounter problems installing or running this release, please 
open an issue in :

     https://gitlab.com/taurus-org/taurus/-/issues


Cheers!


-- 
+----------------------------------------------------+
  Carlos Pascual Izarra
  Scientific Software Coordinator
  Computing Division
  ALBA Synchrotron  [http://www.albasynchrotron.es]
  Carrer de la Llum 2-26
  E-08290 Cerdanyola del Valles (Barcelona), Spain
  E-mail: cpa...@ce...
  Phone: +34 93 592 4428
+----------------------------------------------------+

[tauruslib-devel] Coming release of Taurus (5.0.x)

[Carlos Pascual-I. <cpa...@ce...>]

Hi,

It is about time to finally do the taurus 5.0.0 release (Jul21 milestone).

There are 2 MRs which need to be integrated for this release:

- https://gitlab.com/taurus-org/taurus/-/merge_requests/1217

- https://gitlab.com/taurus-org/taurus/-/merge_requests/1216


Then we can use 1-2 weeks for testing on various platforms and if there 
are no surprises, we could be releasing on the first week of October.

If you think that something is missing or have any other suggestion, 
please say so.

Cheers!

Carlos


-- 

+----------------------------------------------------+
  Carlos Pascual Izarra
  Scientific Software Coordinator
  Computing Division
  ALBA Synchrotron  [http://www.albasynchrotron.es]
  Carrer de la Llum 2-26
  E-08290 Cerdanyola del Valles (Barcelona), Spain
  E-mail: cpa...@ce...
  Phone: +34 93 592 4428
+----------------------------------------------------+

[tauruslib-devel] TEP20: support for multi-models

[Carlos Pascual-I. <cpa...@ce...>]

Hi all,

This message is to announce a new Taurus Enhancement Proposal (TEP20) 
which proposes an implementation for multi-model support in Taurus.

This will affect a very fundamental part of Taurus, so any feedback will 
be appreciated, specially in this DRAFT phase of the TEP.

Please find the TEP20 document in:

https://gitlab.com/c-p/taurus/-/blob/tep20/doc/source/tep/TEP20.md

and leave any comments/suggestions in the following Merge Request 
discussion:

https://gitlab.com/taurus-org/taurus/-/merge_requests/1218

Cheers!

Carlos

-- 
+----------------------------------------------------+
  Carlos Pascual Izarra
  Scientific Software Coordinator
  Computing Division
  ALBA Synchrotron  [http://www.albasynchrotron.es]
  Carrer de la Llum 2-26
  E-08290 Cerdanyola del Valles (Barcelona), Spain
  E-mail: cpa...@ce...
  Phone: +34 93 592 4428
+----------------------------------------------------+

[tauruslib-devel] New release of Taurus 4.8.0 (Jun21)

[Carlos Pascual-I. <cpa...@ce...>]

We are happy to announce the release of Taurus 4.8.0.

This release is relatively modest in terms of new functionality
for the end-user because most of the effort was focused on
project migration to gitlab.com and other developer-oriented
improvements.

This is the last release supporting python2 and Qt4. Work has already begun
to prepare the next major version (taurus 5) and therefore taurus 4.8 will
likely be the last in the 4.x series (no new features are expected to land
on the 4.x series after this release).

For those installing with conda, please note that taurus and all its
dependencies are now distributed via the conda-forge channel:

     conda install -c conda-forge taurus taurus_pyqtgraph

The source files can be downloaded from:

     https://pypi.org/project/taurus/4.8.0/

The documentation (including installation instructions for different 
platforms) is available at:

     http://www.taurus-scada.org

For a detailed list of changes, see the CHANGELOG:

https://gitlab.com/taurus-org/taurus/-/blob/develop/CHANGELOG.md

...and the Jun21 milestone:

     https://gitlab.com/taurus-org/taurus/-/milestones/16

If you encounter problems installing or running this release, please 
open an issue in :

     https://gitlab.com/taurus-org/taurus/-/issues


Cheers!

-- 
+----------------------------------------------------+
  Carlos Pascual Izarra
  Scientific Software Coordinator
  Computing Division
  ALBA Synchrotron  [http://www.albasynchrotron.es]
  Carrer de la Llum 2-26
  E-08290 Cerdanyola del Valles (Barcelona), Spain
  E-mail: cpa...@ce...
  Phone: +34 93 592 4428
+----------------------------------------------------+

[tauruslib-devel] Coming release of Taurus (Jun21)

[Carlos Pascual-I. <cpa...@ce...>]

Hi,

You are probably aware that we didn't do a Jan21 release of taurus and 
instead, we only did a couple of hotfix releases (4.7.1 and 4.7.1.1). 
Now it is time to get moving...

The idea [1] for the Jan21 milestone was to make it the last one of the 
4.x series (i.e., to provide a last release with Python2 and Qt4 support 
and immediately drop them).

Since the amount of available person-power for working on taurus is at a 
minimum (see [2]), I narrowed the scope of the Jan21 Milestone (and I 
renamed it as Jun21[3]). Unless someone suggests to add something extra 
to this Milestone, I'll directly start a release branch and start with 
the tests (debian10+windows-conda unless someone else suggests another).

Once this is done, I intend to devote some time to get a taurus 5.0 
version ready which should be 100% compatible with Jun21 release except 
that py2 and Qt4 would not be supported (i.e. deprecations existing in 
the 4.x series will not be enforced in 5.0)

If you have any comment, suggestion, or want to offer help, please let 
me know.

Cheers!

Carlos


Links:

[1] https://gitlab.com/taurus-org/taurus/-/issues/1041

[2] https://gitlab.com/taurus-org/taurus/-/issues/1140

[3] https://gitlab.com/taurus-org/taurus/-/milestones/16


-- 
+----------------------------------------------------+
  Carlos Pascual Izarra
  Scientific Software Coordinator
  Computing Division
  ALBA Synchrotron  [http://www.albasynchrotron.es]
  Carrer de la Llum 2-26
  E-08290 Cerdanyola del Valles (Barcelona), Spain
  E-mail: cpa...@ce...
  Phone: +34 93 592 4428
+----------------------------------------------------+

[tauruslib-devel] Taurus moving to gitlab

[Carlos Pascual-I. <cpa...@ce...>]

Hi all,

This email is to announce that we are planning to move the taurus 
projects from github.com to gitlab.com

You can see more details and rationale in the TEP19:

http://www.taurus-scada.org/tep/

... and its associated PR:

https://github.com/taurus-org/taurus/pull/1179


Note: In order to attribute comments, issues, statistics, etc to the 
right account in gitlab.com, it is recommended to map the github 
accounts to gitlab accounts. For this reason, if you ever participated 
in some way in a taurus project (even if just by commenting in an 
issue), you may receive a notification with instructions.

Cheers!

-- 
+----------------------------------------------------+
  Carlos Pascual Izarra
  Scientific Software Coordinator
  Computing Division
  ALBA Synchrotron  [http://www.albasynchrotron.es]
  Carrer de la Llum 2-26
  E-08290 Cerdanyola del Valles (Barcelona), Spain
  E-mail: cpa...@ce...
  Phone: +34 93 592 4428
+----------------------------------------------------+

[tauruslib-devel] TEP17 CANDIDATE-->APPROVED voting

[Carlos Pascual-I. <cpa...@ce...>]

Hi all,

This is a request for voting on the approval of the TEP17 (pyqtgraph 
plots). It would be nice if at least one person from each institute 
gives an explicit ok in

https://github.com/taurus-org/taurus/pull/452

Cheers!

Carlos

PS: it is kind of a formality because in practice we are already using 
the taurus_pyqtgraph plugin.


-- 
+----------------------------------------------------+
  Carlos Pascual Izarra
  Scientific Software Coordinator
  Computing Division
  ALBA Synchrotron  [http://www.albasynchrotron.es]
  Carrer de la Llum 2-26
  E-08290 Cerdanyola del Valles (Barcelona), Spain
  E-mail: cpa...@ce...
  Phone: +34 93 592 4428
+----------------------------------------------------+

[tauruslib-devel] New release of Taurus 4.7.0 (Jul20)

[Carlos Pascual-I. <cpa...@ce...>]

We are happy to announce the release of Taurus 4.7.0.

This release brings a lot of changes with respect to 4.6.1, among which 
are improved CLI,
better selection of Qt bindings (Qt5 is now the default fallback), more 
customizable
TaurusGuis, better support for plugins,...

As a novelty, taurus (and taurus_pyqtgraph) can now also be installed 
using conda, with:

   conda install -c taurus-org taurus taurus_pyqtgraph


Also note that this is quite probably the last release officially 
supporting python2.



The source files can be downloaded from:

   https://pypi.org/project/taurus/4.7.0/

The documentation (including installation instructions for different 
platforms) is available at:

   http://www.taurus-scada.org

For a detailed list of changes, see the CHANGELOG:

   https://github.com/taurus-org/taurus/blob/master/CHANGELOG.md

...and the issue tracker:

   https://github.com/taurus-org/taurus/milestone/15?closed=1

If you encounter problems installing or running this release, please
open an issue in :

   https://github.com/taurus-org/taurus/issues

-- 
+----------------------------------------------------+
  Carlos Pascual Izarra
  Scientific Software Coordinator
  Computing Division
  ALBA Synchrotron  [http://www.albasynchrotron.es]
  Carrer de la Llum 2-26
  E-08290 Cerdanyola del Valles (Barcelona), Spain
  E-mail: cpa...@ce...
  Phone: +34 93 592 4428
+----------------------------------------------------+

[tauruslib-devel] The Taurus boat is sinking

[Carlos Pascual-I. <cpa...@ce...>]

I would like to bring your attention to the following critical taurus issue:

https://github.com/taurus-org/taurus/issues/1140

Cheers!


Carlos

-- 
+----------------------------------------------------+
  Carlos Pascual Izarra
  Scientific Software Coordinator
  Computing Division
  ALBA Synchrotron  [http://www.albasynchrotron.es]
  Carrer de la Llum 2-26
  E-08290 Cerdanyola del Valles (Barcelona), Spain
  E-mail: cpa...@ce...
  Phone: +34 93 592 4428
+----------------------------------------------------+

Re: [tauruslib-devel] preparing Taurus Jul20 release (and cancelling Jan20)

[Carlos Pascual-I. <cpa...@ce...>]

Hello,

I created the merge request for the Jul20 release of Taurus (see [1])

Now it is time to test the artifacts in various environments.

I already tested on debian10 (results available in [2]), but I won't be 
available until the end of the month.

It would be very good if someone else could do manual tests in other 
environments following the instructions from [1]  during the next two 
weeks, so that we can release in the first week of august.

Cheers!

Carlos

Links:

[1] https://github.com/taurus-org/taurus/pull/1127

[2] https://github.com/taurus-org/taurus/issues/1128




On 7/13/20 6:45 PM, Carlos Pascual-Izarra wrote:
> Hi,
>
> I regret to say that I did not get a flood of replies, reviews or 
> fixes after my last calls for help with the Jul20 Taurus release. 
> Please note that the team at ALBA that used to do this is now reduced 
> to... mostly me.
>
>   So...
>
>
> **This is a last desperate S.O.S. call for help with the Jul20 Taurus 
> release.**
>
>
> Wednesday is my last day before holidays, and I want to leave a 
> testable release candidate). Therefore Tomorrow (Tuesday) is the last 
> day for merging all the PRs pending to be integrated in the "ready for 
> review" column in [1] .
>
>
> I would very much prefer if someone else reviewed the PRs that I 
> coded, but if that is not the case, I'll self-merge myself.
>
>
> So, please, even if you are not an official "taurus integrator" please 
> pick some PR from the "ready for review" column of [1], and leave a 
> comment with your review of it.
>
> Also, once the release candidate artifact is ready, please help with 
> the manual release tests (see [2])
>
>
> Cheers!
>
> Carlos
>
>
> [1] https://github.com/taurus-org/taurus/projects/3
>
> [2] 
> https://github.com/taurus-org/taurus/blob/develop/doc/how_to_release.md#manual-test-checklist
>
>
>
>
>
>
> On 7/6/20 12:01 PM, Carlos Pascual-Izarra wrote:
>> Hi, in order to facilitate coordination, I created the following 
>> "project":
>>
>> https://github.com/taurus-org/taurus/projects/3
>>
>> Here you can see a kanban table with "to-do", "in progress", "ready 
>> for review" and "done" columns.
>>
>> Please do not be shy and take any task from the "to do" column , 
>> moving it to "in progress" to indicate that you are working on it.
>>
>> Alternatively, just review a task from the "ready for review". After 
>> a satisfactory review, if you have permissions directly merge it,  
>> and , if you don't  just report your review in a comment.
>>
>> Any help would be much much much appreciated!
>>
>> And of course, I'll be happy to help if you have any questions or 
>> need some help in fixing/reviewing a task (just use the comments in 
>> the issue/PR).
>>
>> Cheers!
>>
>> Carlos
>>
>>
>> On 6/30/20 11:06 PM, Carlos Pascual-Izarra wrote:
>>> Hi,
>>>
>>> July is "tomorrow"
>>>
>>> ... meaning that we should hurry to get the release in time.
>>>
>>> I've concentrated efforts lately in removing what I considered the 
>>> main blockers for the new release: the unreliability of the test 
>>> suite and the basic entry-point based plugins. With these two things 
>>> cleared, I think that it is now easier to work on the remaining 
>>> issues planned for the July20 milestone [1].
>>>
>>> Still, unfortunately, it seems clear that we at ALBA won't have 
>>> enough time to solve all the issues currently listed in [1]. 
>>> Therefore I am making a call for help to the rest of the taurus 
>>> community to try to fix as much of those issues as possible until 
>>> the 14th of July (after that we should do the release tests and the 
>>> release itself).
>>>
>>> Please don't be shy!  ;)
>>>
>>> Carlos
>>>
>>>
>>>
>>> On 5/7/20 11:57 PM, Carlos Pascual-Izarra wrote:
>>>> Hi all,
>>>>
>>>> As you probably noticed, this year we broke our promise of 
>>>> delivering the "January" release of Taurus.
>>>>
>>>> This was due to a combination of unexpectedly increased workload, 
>>>> reduction in ALBA's Taurus dev team,  concurrence of several 
>>>> release-critical bugs and plain bad planning from my side (sorry!).
>>>>
>>>> At this point it makes not sense to keep the Jan20 milestone open, 
>>>> so I moved all the tasks to Jul20 and I'll try to concentrate 
>>>> efforts on getting that one ready.
>>>>
>>>> If there is some specific issue that you deem specially important, 
>>>> please comment it in the issue itself so that we can prioritise.
>>>>
>>>> Of course, as usual, any help will be very welcome 
>>>> (reporting/fixing bugs, testing, documenting,...).
>>>>
>>>> Cheers!
>>>>
-- 
+----------------------------------------------------+
  Carlos Pascual Izarra
  Scientific Software Coordinator
  Computing Division
  ALBA Synchrotron  [http://www.albasynchrotron.es]
  Carrer de la Llum 2-26
  E-08290 Cerdanyola del Valles (Barcelona), Spain
  E-mail: cpa...@ce...
  Phone: +34 93 592 4428
+----------------------------------------------------+