GeoMoose issue organization

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

GeoMoose issue organization

James Klassen
I updated the milestones for the gm3 repo to start mapping out 3.3.1/3.4/4.0 mostly based on how I guessed resolving the issues would impact semver rules.  Although my main goal was to try and get a feel for what we can realistically hope to achieve for 3.3.1.

A lot of the issues I added to 3.3.1 appear like they may be already resolved but didn't get closed.  I figure those should be easy (quick verify and click close).

And this isn't ruling out a 3.3.2 either if some fixes are quick and others need more time.

I also created issue #376 to start a discussion on what we are doing with the mobile example.  I'm not sure how much we can do there without forcing a 4.0.

Personally, I feel we as a project would benefit from a bug squashing and documentation sprint (the OSGeo community sprint in May may be a good opportunity for this).



_______________________________________________
geomoose-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geomoose-psc
Reply | Threaded
Open this post in threaded view
|

Re: GeoMoose issue organization

Eli Adam
On Fri, Apr 26, 2019 at 9:24 PM James Klassen <[hidden email]> wrote:
>
> I updated the milestones for the gm3 repo to start mapping out 3.3.1/3.4/4.0 mostly based on how I guessed resolving the issues would impact semver rules.  Although my main goal was to try and get a feel for what we can realistically hope to achieve for 3.3.1.
>

Thanks, accurate labels make it easier to sort through issues.

> A lot of the issues I added to 3.3.1 appear like they may be already resolved but didn't get closed.  I figure those should be easy (quick verify and click close).
>
> And this isn't ruling out a 3.3.2 either if some fixes are quick and others need more time.
>
> I also created issue #376 to start a discussion on what we are doing with the mobile example.  I'm not sure how much we can do there without forcing a 4.0.
>
> Personally, I feel we as a project would benefit from a bug squashing and documentation sprint (the OSGeo community sprint in May may be a good opportunity for this).
>

Yes, this could be good!  I won't be there in person but could join
some of it remotely.

Best regards, Eli

>
> _______________________________________________
> geomoose-psc mailing list
> [hidden email]
> https://lists.osgeo.org/mailman/listinfo/geomoose-psc
_______________________________________________
geomoose-psc mailing list
[hidden email]
https://lists.osgeo.org/mailman/listinfo/geomoose-psc