On Fri, 26 Apr 2024 at 05:36, Markus Neteler via grass-dev <
grass-dev@lists.osgeo.org> wrote:
> The remainder for the 8.4.0 milestone are (currently) 104 open pull
> requests (PRs) which still need testing or review or to be postponed:
>
Hi and welcome Hamed,
On Mon, 18 Mar 2024 at 20:10, Hamed A. Elgizery via grass-dev <
grass-dev@lists.osgeo.org> wrote:
>
> Can you please guide me with any materials — if available — regarding the
> datasets? And if there is an issue “test of skills” available that is
> related to EODAG, since
On Fri, 8 Mar 2024 at 09:10, Ondřej Pešek wrote:
>
> @Vaclav: Do you have some more points against the master-children
> schema? It seems that the general agreement is *for* the restructuring
> into parent and children teams. So far the only point against was "I
> didn't find team nesting
On Sat, 2 Mar 2024 at 07:04, Paulo van Breugel via grass-dev <
grass-dev@lists.osgeo.org> wrote:
>
>
> On March 2, 2024 1:00:23 AM GMT+01:00, Michael Barton via grass-dev <
> grass-dev@lists.osgeo.org> wrote:
> >It's been awhile since I've done this but I thought I remembered that a
> new map
On Tue, 20 Feb 2024 at 04:14, Markus Neteler via grass-dev <
grass-dev@lists.osgeo.org> wrote:
>
> In fact the slowest CI run determines how much time I have to wait
> with each release step (i.e., editing VERSION file, wait 1:30hs, do
> some steps, wait 1:30hs, create tarball, wait 1:30hs, reset
Huidae and Ondrej,
I recently restructured the teams to reflect GitHub workflows and resulting
needs for access (the original team structure was just used from Subversion
access). Another reason was getting a better control over who can change
the code directly (this is connected to the required
On Tue, 20 Feb 2024 at 06:45, Nicklas Larsson via grass-dev <
grass-dev@lists.osgeo.org> wrote:
>
> On 20 Feb 2024, at 10:14, Markus Neteler via grass-dev <
> grass-dev@lists.osgeo.org> wrote:
>
>
> In fact the slowest CI run determines how much time I have to wait
> with each release step (i.e.,
Seeing the new startup screen idea description, the "Proposals for a new
GRASS GIS startup mechanism" wiki page on Trac wiki might be a good read:
https://trac.osgeo.org/grass/wiki/wxGUIDevelopment/New_Startup
On Thu, 15 Feb 2024 at 14:11, Anna Petrášová via grass-dev <
://trac.osgeo.org/grass/wiki/PSC/Minutes/PSC_Meeting_20240209
[2] https://github.com/orgs/OSGeo/projects/2
[3] https://github.com/orgs/OSGeo/teams/grass-write
On Thu, 21 Dec 2023 at 10:45, Vaclav Petras wrote:
> Dear users and developers,
>
> We have a new development which will likely touch every
Dear users and developers,
We have a new development which will likely touch everyone, so I would like
to make sure that everyone is informed and can prepare for or even help
with the changes.
After years of discussions, we are renaming the "location" concept in GRASS
GIS to "project". While we
On Mon, 9 Oct 2023 at 02:41, Martin Landa wrote:
>
> right, the build process was broken. Fixed. Martin
>
Thank you! Looks good. Revision 632b22970e is the latest on main.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
Dear Martin and grass-dev,
The daily build for Windows seems outdated to me. The file at
https://wingrass.fsv.cvut.cz/grass84/
is from today, but the commit hash is df2c0bc922 which is this commit:
https://github.com/OSGeo/grass/commit/df2c0bc922
from June 7. This is the date in the logs.
On Wed, 13 Sept 2023 at 15:13, Markus Neteler wrote:
> Hi,
>
> I have updated doc/infrastructure.md in my local Git copy and fail to
> commit it in a new PR due to pre-commit linting checks:
>
>
> markdownlint.Failed
> ...
>
> I tried
also via mailing lists
>
> Vero
>
> El vie., 1 sep. 2023 10:28, Markus Neteler escribió:
>
>> Hi Vaclav,
>>
>> Just a hint: the email limit can be lifted easily. Just post and I (or
>> any other list admin) can approve it.
>>
>> Markus
>>
>
Dear all,
Having the very nice post about the meeting in Prague and others at the
GRASS website, I was thinking we should send this to the grass-user mailing
list too and maybe grass-dev.
Given the mailing list emails have size limitations and may end up
potentially ASCII, I'm suggesting sending
I'm planning to participate remotely, mostly async. If anyone plans to
participate one way or another, let me know, we can connect.
Best,
Vaclav
On Wed, 2 Aug 2023 at 15:06, Markus Neteler wrote:
> The Annual Code Sprint comes to Vienna (Austria)!
> The OSGeo Community Sprint 2023 will be
On Tue, 8 Aug 2023 at 12:26, Markus Neteler wrote:
> Hi Peter,
>
> On Tue, Aug 8, 2023 at 5:04 PM Peter Löwe wrote:
> >
> > Hi Markus,
> > the licence ID for GRASS GIS 7.8.8. on its landing page reads:
> > "Other (Open)"
>
> I have seen it, too. Unfortunately not the precise licence
Hi Michael,
On Thu, 20 Jul 2023 at 18:14, Michael Barton wrote:
> According to the d.legend.vect manual, I should have a legend file
> somewhere for all vectors. Here is what it says in notes:
>
> "Module d.legend.vect draws vector legend based on legend file defined in
> shell environment
Hi Brendan,
On Sat, 18 Mar 2023 at 23:43, Brendan wrote:
> I would like to join the community sprint this year. Probably remotely,
> but possibly in person.
>
Great! We are planning for a good remote participation option. We still
need to plan the details... (I guess this is the first call for
Hi Stefan,
On Sun, 12 Mar 2023 at 08:45, Stefan Blumentrath
wrote:
>
> After adding another case to the t.rast.algebra test, the tesuite
> occasionally fails due to test time-out. See:
>
> https://github.com/OSGeo/grass/actions/runs/4394593270/jobs/7699431483#step:11:236
> The t.rast.algebra
Dear all,
Please see the current draft of RFC: Version Numbering which is in PR 2357.
It is now almost ready and you can leave comments on GitHub or here. Most
important thing it brings is a continuous minor versioning line, i.e., the
next planned release - as you may have noticed - is 8.3, not
On Tue, 21 Feb 2023 at 13:19, Veronica Andreo wrote:
>
> El vie, 17 feb 2023 a las 15:25, Markus Neteler ()
> escribió:
>
>>
>> Version scheme update: please note that we abandon the odd/even scheme
>> and go for semantic versioning, i.e. 8.3.x comes after the 8.2.x
>> series. See also the
Hi Francesco,
On Wed, 1 Feb 2023 at 07:09, Francesco Paolo Lovergine
wrote:
>
>
> ...or change quantile and quartile into a list of 1..2 comma separated
> values.
>
> Much better, isn't it?
>
Maybe, but explicit named arguments are nice, too.
Do you plan to open a PR? A more experimental code
If you want to join the sprint planning meeting in an hour or so, you need
to email me to get the link.
If you already got the link from me or as a PSC member, you can ignore this
email.
___
grass-dev mailing list
grass-dev@lists.osgeo.org
at 14:03, Vaclav Petras wrote:
> Dear all,
>
> I'm happy to announce we are planning a community sprint for the 40th
> birthday of GRASS GIS!
>
> If you are interested, we will meet on Friday, February 17 at 15:00 UTC
> [1]. Send me an email and I will send you a Zoom link.
>
Dear all,
I'm happy to announce we are planning a community sprint for the 40th
birthday of GRASS GIS!
If you are interested, we will meet on Friday, February 17 at 15:00 UTC
[1]. Send me an email and I will send you a Zoom link.
Best,
Vashek
[1]
On Mon, 5 Dec 2022 at 08:07, Nicklas Larsson via grass-dev <
grass-dev@lists.osgeo.org> wrote:
>
> 1. We adapt the formatting policy using ClangFormat.
>
+1
I would prefer if formatting changes from GNU indent which can be done
separately are done separately. For Python & Black, I did that
On Tue, 22 Nov 2022 at 14:54, Nicklas Larsson via grass-dev <
grass-dev@lists.osgeo.org> wrote:
> ...In case that is the way the community choose to go then the label will
> have to be “backport releasebranch_8_2”, which is very long…
>
We could revisit the names of branches. The word branch
Dear all,
GNU indent is confused by code in dglib/misc-template.c and I can't really
blame it. I'm confused, too. It is hard to track the structure there.
indent says (also reported in #1630):
indent: ./lib/vector/dglib/misc-template.c:574: Error:Stmt nesting error.
indent:
Hi Jorge and all,
Are there any other accounts which need the same steps? E.g., YouTube?
Thanks,
Vaclav
On Tue, 8 Nov 2022 at 04:38, Markus Neteler wrote:
> Hi Jorge,
>
> On Mon, Nov 7, 2022 at 7:59 PM Jorge Cornejo wrote:
> >
> > Is there anyone from GRASS that can officially take over this
On Thu, 27 Oct 2022 at 12:35, Markus Neteler wrote:
> On Thu, Oct 27, 2022 at 5:32 AM Vaclav Petras
> wrote:
> >
> > I'm adding some new material to the grass-promo repository [1]. I can
> also share some of the designs through Sticker Mule, too, so ask me if you
> w
Dear all,
I'm adding some new material to the grass-promo repository [1]. I can also
share some of the designs through Sticker Mule, too, so ask me if you want
some.
I took the opportunity and added a trivial readme file which may clarify
when to add things to it (that is any time). While with
On Thu, 13 Oct 2022 at 15:43, Markus Neteler wrote:
> On Thu, Oct 13, 2022 at 8:35 AM Brad ReDacted
> wrote:
> >
> > Can someone tell me what spec the (enhanced) postscript driver
> > (lib/psdriver) adheres to? I am having difficulty looking up one of the
> > parameters (box erase, in
On Fri, 7 Oct 2022 at 16:59, Daniel Torres wrote:
>
> I'd say it would be good to create some issues for non coding enthusiasts
>
Here is one. It is the "will stay open forever" type.
https://github.com/OSGeo/grass/issues/2594
___
grass-dev mailing
On Fri, 7 Oct 2022 at 09:18, Daniel Torres wrote:
>
> I see that all issues tagged with 'Hacktober' are coding related, do you
> guys have any idea of non coding stuff that could work? like first-issue
> but non coding? mmm I don't know, documentation, missing examples, and so
> on?
>
Images
On Thu, 6 Oct 2022 at 13:46, Daniel Torres wrote:
> Hi guys,
> are we doing anything for hacktober? I see some 2021 issues in the grass
> repo tagged as hacktober,
>
...and the grass and grass-addons repos are tagged and I'm ready to do some
reviews. I just didn't have any capacity to do the
Hi Stefan,
On Wed, 5 Oct 2022 at 07:18, Stefan Blumentrath
wrote:
>
> Test success rate is at ~70 % and if I add a new failing test, that is
not considered a test failure, so I have to go in and check if the added
test actually succeeded.
The tooling improved since the rule was set up, so I
Hi Stefan,
On Wed, 5 Oct 2022 at 07:31, Stefan Blumentrath
wrote:
>
> ... come up with a suggestion for how to implement (including opt-out /
opt-in possibilities)...
I thought pre-commit hooks are always opt-in. In any case, that's probably
the first thing which would inform other decisions.
On Sat, 17 Sept 2022 at 04:57, Wolf Bergenheim
wrote:
> On Tue, 13 Sept 2022 at 09:33, Vaclav Petras wrote:
>
>>
>> Formatting needs to be enforced in the CI. This can be done with
>> something like re-indent followed by git diff.
>>
>>
> Maybe som
be done with something
like re-indent followed by git diff.
Best,
Vaclav
On Sat, 27 Aug 2022 at 14:06, Vaclav Petras wrote:
> Dear all,
>
> Most of the C and C++ code was indented using our
> ./utils/grass_indent_ALL.sh script at the FOSS4G 2022 sprint. This will
> help to inde
Dear all,
Most of the C and C++ code was indented using our
./utils/grass_indent_ALL.sh script at the FOSS4G 2022 sprint. This will
help to indent code for PRs and with the transition to clang-format.
Directories with files which indent reports issues for were not updated,
because more changes
On Wed, Aug 24, 2022, 4:51 AM Martin Landa wrote:
> Hi Vaclav,
>
> st 24. 8. 2022 v 10:41 odesílatel Vaclav Petras
> napsal:
>
>> The lib/gis/parser_html.c puts iso-8859-1 into the HTML files (I just
>> checked that now), so that's what an HTML reader should be
Hi Martin,
On Wed, 24 Aug 2022 at 04:25, Martin Landa wrote:
>
> the question is also why we are using default OS encoding to decode HTML
> pages [1]. Couldn't we simply use UTF-8 regardless of OS system locale?
>
This seems to be some general confusion around that, or more likely just
some
Now, I see I misunderstood here. The Discussion is about the communication
channels, not about the website. I guess my comments are still generally
valid, but irrelevant here. Sorry for the noise.
On Mon, 1 Aug 2022 at 14:58, Vaclav Petras wrote:
> ...but I should add: Let's see what wo
...but I should add: Let's see what works.
On Mon, 1 Aug 2022 at 14:56, Vaclav Petras wrote:
> There is no difference in discussing things in the PR or issue versus in a
> Discussion in terms of notifications, no? If it is about development, it
> should be part of this mailing list o
rote:
>>>>>
>>>>>> Hi Daniel,
>>>>>>
>>>>>> Welcome! Besides what Vashek pointed out, if you feel comfortable
>>>>>> starting with something for the website, we are missing a search engine
>>>>>&g
Hi Daniel,
Welcome. That sounds great. For Python, check this presentation I'm
preparing for FOSS4G where are I describe how to do good PRs which fix
coding standards and the load of tools which can be applied:
https://wenzeslaus.github.io/code-quality-measures-foss4g-2022/#/45
JavaScript at
To celebrate GRASS birthday, discuss latest developments, and more, join us
in one hour using Zoom at:
https://ncsu.zoom.us/j/92129342971?pwd=Um1DSlhtYWwrL3Vwa0tlc3hzNHBQdz09
Topic: GRASS GIS Birthday 2022
Time: 15:00 UTC
Meeting ID: 921 2934 2971
Passcode: 454117
On Thu, 28 Jul 2022 at 03:33,
On Mon, 25 Jul 2022 at 23:38, Brad ReDacted
wrote:
>
> Is there any objection to adding yet another dependency?
>
To keep this moving, I think there are no objections to adding security if
the new dependency is optional. Optional dependencies and maintainable code
is generally a good start to
On Mon, 25 Jul 2022 at 23:38, Brad ReDacted
wrote:
>
> I hate adding dependencies, but security is best left to security
> experts and I strongly advocate against duplicating security related code.
>
If this security feature is really needed, then the best practices seem to
indicate a
I'm pleased to announce that GRASS GIS 8.2.0 was released!
The 8.2.0 release of GRASS GIS is now available with results from the GSoC
2021 and many other additions. A new grass.jupyter package is now included
for interacting with Jupyter notebooks. Single window graphical user
interface is
the
>> website yet and does not make sense to post about it... difficult day
>> yesterday, sorry
>>
>> Vashek, if you want to merge the release news then go ahead, I tweet
>> about that and on thursday, we do Caitlin post when it appears online.
>>
>> Vero
&g
On Sat, Jun 4, 2022, 5:07 PM Veronica Andreo wrote:
>
> I had planned to merge Caitlin's news tomorrow and tweet about that on
> Monday, so then we can post the release,
>
That works for me!
>
___
grass-dev mailing list
grass-dev@lists.osgeo.org
On Sat, 4 Jun 2022 at 16:20, Martin Landa wrote:
>
> standalone installer available for testing at
>
>
> https://grass.osgeo.org/grass82/binary/mswindows/native/WinGRASS-8.2.0-1-Setup.exe
>
Thank you, Martin!
___
grass-dev mailing list
There are 2-3 open PRs, one bug fix and some release procedure things,
which will go in before the final release.
https://github.com/OSGeo/grass/milestone/8
Best,
Vaclav
On Sun, 1 May 2022 at 15:01, Vaclav Petras wrote:
> Dear all,
>
> New planned dates for 8.2.0 [1]:
>
> M
On Fri, 6 May 2022 at 18:04, Martin Landa wrote:
>
> Windows standalone installer
>
Thank you, Martin!
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
/wiki/RFC/4_ReleaseProcedure
[3]
https://mybinder.org/v2/gh/OSGeo/grass/8.2.0RC1?urlpath=lab%2Ftree%2Fdoc%2Fnotebooks
On Fri, 29 Apr 2022 at 09:34, Vaclav Petras wrote:
> Dear all,
>
> 8.2.0RC1 was released.
>
> https://github.com/OSGeo/grass/releases/tag/8.2.0RC1
>
> Pl
Dear all,
8.2.0RC1 was released.
https://github.com/OSGeo/grass/releases/tag/8.2.0RC1
Please test and package it as you see fit.
Best,
Vaclav
___
grass-dev mailing list
grass-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/grass-dev
Hi Brad,
On Tue, 26 Apr 2022 at 12:37, Brad ReDacted
wrote:
> Hello,
>
> Is there any particular reason lib/rast3d/error.c exists? All I see is
> duplicated functionality to lib/gis/error.c with different function
> names.
>
I think the general idea there is that the rast3d library uses a
).
Creation of the release branch also means that the main branch is now ready
for larger changes.
Best,
Vaclav
[1] https://github.com/OSGeo/grass/tree/releasebranch_8_2
[2] https://github.com/OSGeo/grass/milestone/8
On Wed, 23 Mar 2022 at 11:52, Vaclav Petras wrote:
> Here is the current st
Merged into the main branch as adde62ef.
https://github.com/OSGeo/grass/commit/adde62ef22bad90c337580afff925be4e646abe2
On Tue, 12 Apr 2022 at 10:09, Vaclav Petras wrote:
> Given that the original motivation is unknown and that we would not do the
> same now, i.e., we would treat GDAL
Unfortunately, v.out.lidar is not built in the CI, so not a good candidate
here, try r.contour, r.in.gdal, v.what, g.search.modules, anything in
gunittest. pygrass or temporal might be more difficult, but still not that
special.
On Mon, 18 Apr 2022 at 13:02, Adithya Ambapurkar wrote:
> I have
Great. I have left a new round of reviews.
#2311 looks hopeful and #2310 is not necessary, so no further changes are
needed in either at this point. Focus on fixing some tests.
On Mon, 18 Apr 2022 at 09:20, Adithya Ambapurkar wrote:
> I have created pull requests for
On Sun, 17 Apr 2022 at 07:30, Adithya Ambapurkar wrote:
> ...used %%python...
>
As I mentioned earlier, I don't recommend this approach, but yes, you can
(and have to) use this in the notebook. However, that's for the notebook
only. Unrelated to the actual test code.
> It ran all tests
If the test run okay and doesn't fail, go ahead and create a PR to enable
it.
Don't try to convert any tests to pytest. That's a topic for the summer.
You should write a new possibly simple test using pytest.
On Sun, Apr 17, 2022, 7:30 AM Adithya Ambapurkar wrote:
> I have selected
On Fri, 15 Apr 2022 at 03:49, Adithya Ambapurkar wrote:
> I have selected test_gunittest_doctests.py file
>
Perhaps try something else. This one may have additional challenges because
it is doctest. Although it actually runs for me in Binder without errors.
> and tried to run on jupyterlab on
solved in GDAL.
On Thu, 7 Apr 2022 at 11:10, Vaclav Petras wrote:
> Hi devs,
>
> We are about to remove dynamic loading of GDAL from the raster library
> code in #2290. GDAL will then be loaded as any other library by the system.
>
> https://github.com/OSGeo/grass/pull/
Hi devs,
We are about to remove dynamic loading of GDAL from the raster library code
in #2290. GDAL will then be loaded as any other library by the system.
https://github.com/OSGeo/grass/pull/2290
Currently, the libraries are loaded with dlopen and LoadLibrary and
GDAL_DYNAMIC is set to enable
Hi Adithya,
Welcome to the grass-dev mailing list. I'll answer inline:
On Wed, 6 Apr 2022 at 11:03, adinayyu wrote:
> ...my statement of proposal for the osgeo grass gis project.
Good topic. The pytest is important!
> How and what should i contribute to the project or osgeo before
submitting
me know if you are interested in having a call about the upcoming
releases.
Best,
Vaclav
8.0.2 https://github.com/OSGeo/grass/milestone/15
8.2.0 https://github.com/OSGeo/grass/milestone/8
On Sun, 27 Feb 2022 at 15:33, Vaclav Petras wrote:
> TLDR: 8.2.0 with GSoC 2021 work (single window, Jupy
On Mon, 21 Mar 2022 at 10:01, Nicklas Larsson via grass-dev <
grass-dev@lists.osgeo.org> wrote:
> ...There were attempts to do this [2, 3], but numerous problem
> arose...which are based on GNU Indent [4]. These problem are probably
> originate in the comparatively limited functionality and lack
On Fri, 4 Mar 2022 at 10:09, Nicklas Larsson via grass-dev <
grass-dev@lists.osgeo.org> wrote:
> Couldn’t the desired outcome
> of using GRASS_NOTIFY be implemented in another way?
>
The purpose was interactive use from the command line I suppose, so for
these cases users can set a convenient
TLDR: 8.2.0 with GSoC 2021 work (single window, Jupyter, parallel modules)
is scheduled for April 5.
Action items: For PRs, merge now or move the milestone to 8.4.0. For
issues, create a new PR now or move to 8.4.0.
Dear all,
We are entering a preparation phase for 8.2 release. (As you may or
On Fri, 25 Feb 2022 at 09:07, Sebastiaan Couwenberg
wrote:
>
> If we want to stop using --prefix=/usr/lib and have FHS complianance
> while also having the shared libraries in the default library search
> path several changes in GRASS will be required.
>
> The resulting structure should result
On Fri, 25 Feb 2022 at 01:25, Sebastiaan Couwenberg
wrote:
> On 2/24/22 15:23, Vaclav Petras wrote:
> > On Thu, 24 Feb 2022 at 03:33, Sebastiaan Couwenberg wrote:
> >> Should we perhaps take this opportunity to move the grass libraries to
> >> default library search pa
Hi Bas,
On Thu, 24 Feb 2022 at 03:33, Sebastiaan Couwenberg
wrote:
>
> Should we perhaps take this opportunity to move the grass libraries to
> default library search paths as raised on the debian-gis list?
>
> https://lists.debian.org/debian-gis/2021/12/msg00023.html
>
I vote yes. I think
On Wed, 23 Feb 2022 at 16:47, Helmut Kudrnovsky wrote:
> >However, there are still a number of 8.0.1-labeled PRs open:
> >
> https://github.com/OSGeo/grass/issues?q=is%3Aissue+milestone%3A8.0.1+is%3Aopen
>
> [Bug] winGRASS is missing PROJ utilits (proj, cs2cs) bug Windows
> [Bug] Broken "List
On Wed, 23 Feb 2022 at 12:37, Markus Neteler wrote:
> On Sun, Feb 20, 2022 at 2:06 PM Markus Neteler wrote:
> >
> > Hi devs,
> >
> > (8.0.1 milestone: https://github.com/OSGeo/grass/milestone/9)
> >
> > I still see backport candidate(s) in
> > -
>
On Wed, 23 Feb 2022 at 04:56, Brad ReDacted
wrote:
>
> I'm going to cc: the list because I'm not sure how to address this.
>
Thanks. That's actually the right thing to do. :-) See also:
https://grasswiki.osgeo.org/wiki/Mailing_list_etiquette#Responding_to_other_posts
On Mon, 14 Feb 2022 at 14:22, Veronica Andreo wrote:
>
> Currently, there's a link to releases in the first entry of
> https://grass.osgeo.org/download/ that points to
> https://github.com/OSGeo/grass/releases. I agree that esp for 8.0.0 the
> link to the tarball means a lot of browsing down.
>
Hi Michael,
This looks more like a grass-dev topic, than grass-psc. I'm adding
grass-dev, please remove grass-psc when (if) you reply.
I'll let others comment on the tarball and website and comment on the Git
and GitHub part. +1 for Nickals' answer.
Git is definitely a valid way of getting
How to edit and fine-tune release descriptions?
I have noticed that the lines for the two v.db.select PRs related to JSON
and CSV were confusing because the JSON mentioned a flag which was later
replaced, so I edited the description of the RC2 release on GitHub. Is that
the right approach?
On Tue, Jan 11, 2022 at 12:52 PM Veronica Andreo
wrote:
>
> El dom, 9 ene 2022 a las 16:36, Markus Neteler ()
escribió:
>>
>> Can we now publish "final" or do we still need a RC2?
>
> With no blockers, I'd be in favor of publishing final already :)
> Is there any "policy" regarding the number of
On Fri, Dec 10, 2021 at 7:39 AM Martin Landa wrote:
>
> most of the workflows in my latest PR are queued because of [1]. Any
> idea what could be wrong? `ubuntu-20.04` is defined in [2].
>
The first link leads me to "Python Flake8 Code Quality" (flake8), but since
you are mentioning
On Wed, Dec 1, 2021 at 4:01 PM Markus Neteler wrote:
> On Wed, Dec 1, 2021 at 9:25 PM Markus Neteler wrote:
> ...
>
> > Drawback: how to filter out the "old" stuff (we seek the delta between
> > 7.8.6 and releasebranch_8_0) - any idea?
>
> Just found out that tags can be compared (sorry for
On Sun, Nov 28, 2021 at 1:06 PM Markus Neteler wrote:
> On Wed, Nov 24, 2021 at 2:10 PM Veronica Andreo
> wrote:
>
> For populating this page I usually use "git log":
>
> # GRASS GIS 7.0.0 release on 2015-03-20
> git log --oneline --after="2015-03-20" | cut -d' ' -f2- | sed 's+^+ *
> G80:+g' |
Dear all,
As decided at the PSC meeting on Friday, I have created a new branch for
the 8.0 release. This means that:
1) We are close to 8.0 RC 1.
2) Version 8 specific bug fixes need to be backported from main to
releasebranch_8_0.
3) If we plan another bug fix release of 7.8, bug fixes
We are having an ad hoc hybrid sprint now. You can connect remotely with
Zoom right now using this link:
https://ncsu.zoom.us/j/97331377857?pwd=Nzh1cW1yaGFXNkxUYVZFQ2Y3bzA5QT09
Best,
Vaclav
___
grass-dev mailing list
grass-dev@lists.osgeo.org
Bergenheim
> wrote:
>
>> Hey Vaclav,
>>
>> Sure, perl is by no means an area I know much about, but looks quite
>> simple :)
>>
>> *-- *
>> * ^.___*
>>
>> *( ,__// / Wolf Bergenheim*
>>
>>
>>
>> On Sat, 2 O
On Fri, Oct 1, 2021 at 10:31 AM Wolf Bergenheim
wrote:
> Mainly I'm looking for opportunities to contribute after 10 years away :P
>
Hi Wolf,
If you are looking for suggestions, there are some Perl linting issues in
grass-addons repo I just stumbled across.
Dear all,
We are having a community sprint on Saturday, October 2nd, 2021.
It is organized by the FOSS4G 2021 conference, but you don't need to be
registered to the conference to participate. Links for meetings will be
posted on the following wiki page or here.
Starting in 1 hour. Here is the link to the call.
https://ncsu.zoom.us/j/96809444905?pwd=VlY5ajZneDhWaUlVZUtFKzFvdWpEdz09
On Fri, Sep 10, 2021 at 9:37 AM Veronica Andreo
wrote:
> Dear all,
>
> Next Tuesday, September 14th at 21:00 CEST [1] we'll (videocall) meet to
> discuss/coordinate
On Fri, Sep 10, 2021 at 3:02 AM Maris Nartiss wrote:
> 2021-09-10 5:56 GMT+03:00, Vaclav Petras :
...
> = Not a big difference from existing implementation
>
Just to be clear, all these would be in addition to the proper handling of
band references and applied only when you don't wan
On Fri, Sep 10, 2021 at 4:36 PM Markus Metz
wrote:
>
> ...all the previously timed-out tests for the affected PRs are passed...
>
As for the timed-out tests - those which are running actual test suites and
time out after 6 hours - that's actually still an issue. It just usually
does not happen.
On Fri, Sep 10, 2021 at 2:30 PM Markus Metz
wrote:
>
> The commit history of the PR has not been messed up, only the relevant
> commits are shown.
>
Right, right, Git or GitHub recognizes that thoise 41 are already on main.
The reason for the rebase was that some tests were failing, apparently
On Fri, Sep 10, 2021 at 1:16 PM Markus Metz
wrote:
> ...
> $ git checkout raster_tempdir
> $ git rebase main
>
> Successfully rebased and updated refs/heads/raster_tempdir.
>
> $ git status
> On branch raster_tempdir
> Your branch and 'metzm/raster_tempdir' have diverged,
> and have 48 and 7
On Thu, Sep 9, 2021 at 3:23 PM Maris Nartiss wrote:
> 2021-09-09 19:19 GMT+03:00, Vaclav Petras :
> >
> > In the documentation, we moved from (5 calls):
> >
> > ```
> > g.region raster=lsat7_2002_10
> > i.group group=lsat7_2002 subgroup=res_30m input=
On Thu, Sep 9, 2021 at 4:46 AM Maris Nartiss wrote:
> Hello Anna, Veronica.
>
> 2021-09-08 23:09 GMT+03:00, Veronica Andreo :
>
> > Indeed, we have a problem if all examples using Landsat will stop working
> > in grass 8, so if this is the case, then we might need a new version of
> the
> >
Hi Ondrej,
On Sat, Sep 4, 2021 at 3:24 AM Ondřej Pešek wrote:
>
> Currently, there is no GRASS 8 branch in the addons repo. Is there a plan
> to create one, or are the changes considered too minor to open a new branch
> for that?
>
The plan is to create one. You can follow the progress here:
Awesome!
I'm not suggesting to do it right now, but for the future, what do you
think about adding more warnings/errors? There is, for example,
-Wunused-result or -Wunused-but-set-variable which we have in the code.
warning: ignoring return value of ‘fread’, declared with attribute
1 - 100 of 1469 matches
Mail list logo
