<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
I see is that there are two competing categorizations of milestones:<br>
<br>
1) We plan to address this issue (ticket/feature/etc.) in x.y.z
version. These are primarily used for release progress tracking.
Ideally these would be all very concrete things, and ideally make
the release when all the issues in the milestone are completed.
This can need to get updated if there is something critical fixed
that forces another release sooner, but generally, this is how I see
this style of milestone working.<br>
<br>
2) More futuristic things that are either general plans or features
we want but haven't figured out how to approach and/or features
where nobody has stepped up to supply either the code (or the funds
for someone to write the code) to get it done. These are hard to
assign to versions because we don't know when the work will be
done. At the moment, these issues don't really fit a milestone (and
I generally leave the milestone unassigned), but it would be nice to
somehow track priority and/or work effort expected to be required.
Maybe we need some sort of list of items we are actively seeking
help with? Maybe some of them should get some sort of code/funding
drive behind them? Otherwise, things only tend to get done when
someone volunteers to do it - which isn't generally very project
release schedule oriented.<br>
<br>
"#47 feature editing" is an example of one of these. (Most of) the
underlying structure exists to support feature editing being
implemented in 3.6 (or possibly even as an add-on to 3.5). The
Drawing/Markup layer already does geometry editing (although likely
not attribute editing), and already can upload/download features as
GeoJSON and KML. The tools should work on the other vector layer
types as well (and would just need to be enabled for that layer).
The real issue is uncertainty about server side software
implementing OGC standard editing protocols and so not knowing what
to target to "save" the changes as a general case solution. Maybe
we don't need a general solution? If we give up on standards and
roll our own, I suspect the easiest thing for GeoMoose would be for
a server to accept GeoJSON over a REST style API.<br>
<br>
So, this one isn't marked as a 4.0 milestone because it can't be
done until 4.0. The 4.0 milestone is just code for we think it is
important and we might get to it sometime in the not-immediate
future. This isn't very helpful for release planning (should the
release manager hold a 4.0 release hostage if it doesn't include
editing, but includes a bunch of other worthy stuff?), nor is it
really communicating that this is something that could be done at
any time given the how it should communicate is figured out and we
are looking for someone to supply code (or funds for code).<br>
<br>
Another thing is I know Dan has some ideas for structural changes
related to updating how react/redux are used that are intended to
clean up some messiness in managing internal state that will likely
be part of a 4.0. And that these changes might make some of the
features people want a lot easier to implement.<br>
<br>
So, the question to me becomes how do we communicate priorities and
importance of these type 2, longer range goals that don't really fit
into the type 1, issue N will be in version X.Y.Z model of
milestones?<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 1/26/20 3:19 PM, Dan Little wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CABqPoBYoJot14xf9W6JwuSLzctLTq-_T69U8kVnVS_d-DX5yaw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>I've tried to create milestones for logical semver
versions.</div>
<div><br>
</div>
<div>- If something will require breaking changes or major
codebase updates, goes to milestone 4.0.0</div>
<div>- New feature goes to 3.X.0</div>
<div>- Bug fix / documentation fix : Goes to 3.[current].Y</div>
<div><br>
</div>
<div>We may be behind on filing all of that.<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Jan 17, 2020 at 3:23
PM Eli Adam <<a href="mailto:eadam@co.lincoln.or.us"
moz-do-not-send="true">eadam@co.lincoln.or.us</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi
all,<br>
<br>
How do we classify milestones on issues?<br>
<br>
<a
href="https://github.com/geomoose/gm3/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+milestone%3A3.5.0"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/geomoose/gm3/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+milestone%3A3.5.0</a><br>
shows only a few things<br>
<br>
Looking at all the open issues,<br>
<a
href="https://github.com/geomoose/gm3/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/geomoose/gm3/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen</a><br>
there are a few more. Trying to update the legend display and<br>
eventually found this, <a
href="https://github.com/geomoose/gm3/issues/324"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/geomoose/gm3/issues/324</a><br>
That probably isn't worthy of a 3.5.0 milestone but some other
ones<br>
might be.<br>
<br>
Best regards, Eli<br>
_______________________________________________<br>
geomoose-psc mailing list<br>
<a href="mailto:geomoose-psc@lists.osgeo.org" target="_blank"
moz-do-not-send="true">geomoose-psc@lists.osgeo.org</a><br>
<a
href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a></blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
geomoose-psc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:geomoose-psc@lists.osgeo.org">geomoose-psc@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/geomoose-psc">https://lists.osgeo.org/mailman/listinfo/geomoose-psc</a></pre>
</blockquote>
<br>
</body>
</html>