Changes between Version 15 and Version 16 of PSC/Minutes/PSC_Meeting_20220513


Ignore:
Timestamp:
May 13, 2022, 10:21:36 AM (2 years ago)
Author:
wenzeslaus
Comment:

More precision for RFCs, more details elsewhere

Legend:

Unmodified
Added
Removed
Modified

  • PSC/Minutes/PSC_Meeting_20220513

    v15 v16  
    3333
    3434- Draft RFCs:
    35   - We are good with the one about Python
    36   - Releases:
     35  - We are good with the one about Python.
     36    - Move to PR.
     37    - Describe the practical aspect when support is dropped on the main branch before the release happens.
     38  - Releases:
    3739    - Shall we keep the RCs system when all changes go through PRs?
    38     - Shall we try to form a testing group of students (many of us do not find the bugs that users do)? This would require a proper guideline to test. We are thinking mostly about testing if binaries actually work in different environments.
     40    - Shall we try to form a testing group (students, users)? (Developers and power users tend to not find the bugs that beginner and intermediate users do.) This would require a proper guideline to test. We are thinking mostly about testing if binaries actually work in different environments.
    3941    - Make 2nd RC optional?
    4042    - Freeze makes more sense for branching, and esp. for major and minor versions, but not for micro releases which are by definition only fixes.
    4143    - Soft freeze = feature freeze, no more new features. Hard freeze = code freeze, no more changes and tag the release.
    42     - Anna and Vashek simplify/rewrite RFC 4.
     44    - Vaclav: simplify/rewrite RFC 4, move to PR.
    4345  - Version numbering:
    4446    - Start using all the numbers (odd and even) for releases.
    45     - Vashek will update the RFC and initiate the motion
    46 - Move trac RFCs to github to keep all of them in on place (Anna?), we tag them for discussion and then create motions via email to vote.
    47 - GSoC 2022: No students for this year
    48 - Results about student grants: Vashek commented that Caitlin was very happy with it. GSoC finishes in August, so after that would be a good timing.
     47    - Vashek will update the RFC in relation to fixed (frozen) code for a release, change status to Ready (?), and initiate the motion.
     48- Move Trac RFCs to !GitHub to keep all of them in on place (Anna). In general, we tag them for discussion and then create motions via email to vote.
     49- GSoC 2022: No students for this year. Two applied. None passed coding challenges.
     50- Results about student grants: Vashek commented that Caitlin was very happy with it. GSoC finishes in August, so after that would be a good timing for next round.
    4951- Vero commented on the follow ups
    5052  - no contracts needed for sponsors, so green light to create different types/categories of sponsors
    51   - Updates about rgrass
     53  - Updates about rgrass (all is well, rgrass7 will be replaced by rgrass)
    5254- Releases:
    5355  - 7.8.8 in the pipeline
    5456  - 8.0.2 is out
    55   - 8.2.0 due by 5 days, but there's the leaflet bug which seems a major showstopper.
     57  - 8.2.0 due by May 20, RC2 is overdue couple days, but there's a Jupyter-related bug which seems a major showstopper, so we need to fix that.
    5658- Weblate vs Transifex
    5759  - weblate automatically creates PRs so we prefer it
    5860  - send out a call to translators to move to weblate (Huidae)
    5961- GRASS in Windows:
    60   - Status of PDAL and openMP support in Windows
    61   - GRASS does not start in some windows computers because of permission issues: windows wants writing permission over grass.py (seems to affect only standalone installer)
     62  - Status of PDAL and OpenMP support in Windows. PDAL is a priority, OpenMP not so much.
     63  - GRASS does not start in some Windows computers because of permission issues: Windows wants writing permission over grass.py (seems to affect only standalone installer)