Add issues and decide due date for Milestone v0.1.0

[Censacrof]

I have just created the Milestone v0.1.0 so that we can plan our first release and the features that it will have.

We need to do 2 things:

1. Define our expectations for this release and decide which issues to add to the milestone (maybe create new ones).
2. Decide the due date. For the moment I have set it to the 16th of December, because to me it seems a reasonable date, of course it is something we need to discuss together.

Also, as said in issue #31, we should really define our release cycle.

One of the reasons that I created the milestone is that the unicom-ig has become a dependency for WP6, WP8 and probably more. In order to plan our activities we need to know the date of the first release of this specification.

[costateixeira]

Thanks. I think we should either decide due dates or scope. Not both. I would plan this differently - let's see which parts are actually critical - and from those parts, decide the minimum scope. Then we plan dates. With this project I would not make assumptions that the requirements are clear and we know the scope.

…

On Fri, Nov 18, 2022 at 4:40 PM Francesco Galisi ***@***.***> wrote: I have just created the Milestone v0.1.0 so that we can plan our first release and the features that it will have. We need to do 2 things: 1. Define our expectations for this release and decide which issues to add to the milestone (maybe create new ones). 2. Decide the due date. For the moment I have set it to the 16th of December, because to me it seems a reasonable date, of course it is something we need to discuss together. Also, as said in issue #31 <#31>, we should really define our release cycle. One of the reasons that I created the milestone is that the unicom-ig has become a dependency for WP6, WP8 and probably more. In order to plan our activities we need to know the date of the first release of this specification. — Reply to this email directly, view it on GitHub <#50>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD3HUUBXXZBYHH4EDSTLS3TWI6PQRANCNFSM6AAAAAASETYOXA> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Censacrof]

Thanks. I think we should either decide due dates or scope. Not both.
I would plan this differently - let's see which parts are actually critical

• and from those parts, decide the minimum scope. Then we plan dates.

With this project I would not make assumptions that the requirements are
clear and we know the scope.

@costateixeira I agree with you, but we need both scope and dates. The two possible approaches are:

1. let's decide what we want to do for the first release and then decide the release date
2. let's decide the release date and then let's see what features we can do with the time we have left

Just like you, I personally like the first approach but we also need to be fast in deciding the release date, many people need to plan based on this decisions.

[rlindstrm]

If you don't specify the scope, you can set the due date to today. :)

But more seriously, is this milestone a boys' thing or is there something you expect me to achieve, as well?

[Censacrof]

If you don't specify the scope, you can set the due date to today. :)

But more seriously, is this milestone a boys' thing or is there something you expect me to achieve, as well?

@rlindstrm of course it's not a boys' thing, it regards everybody in the UNICOM project. A Milestone is basically a collection of Issues with a due date attached, we use it to plan what to add / fix before the next release of the unicom-ig.

I would like you, as anyone contributing to this repository, to participate in the decision about scope and due date of the release.

I propose that we start by adding issues to the milestones and in the first half of the technical meeting next week, we decide which issues to remove from the milestone, which to add, and create new ones if needed. In the second half of the meeting we can decide the due date.