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

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

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
+----------------------------------------------------+