I think we all agree that setting a date for the next release is
mandatory, but nobody of the candidates has the adequate time for that job.
Maybe we could start by picking the issues/tasks we want to have have/do
in/for 2.9. We talked about creating a GitHub project
<https://docs.github.com/en/issues/organizing-your-work-with-project-boards/managing-project-boards/about-project-boards>
to chose the issues to get an overview what has to be done for the 2.9
release. That would make it easier to estimate a deadline.
Andy, should I assist you by creating such a project?
We can discuss the task further in the next meeting, I already set it on
the agenda of the next meeting.
Hans
Am 10.08.22 um 20:14 schrieb Chris Morley:
We seem to all agree that 2.9 (or whatever) is reassembly close.
Why not make the 2.9 branch now?
To get things done you must set a GOAL and a DATE.
We have done neither.
For instance I am not going to go through all my configs in master.
i have configs I want in master but will prune for 2.9.
If there was a 2.9 branch I would prune them now.
It would also allow us to merge master stuff (classicladder!) into master.
It we had done that months ago then we could now probably back port it to 2.9
reasonably bug free about now.
We have traditionally talked for months (years even) on releasing, then one
random weekend someone finds the time to do it and it ends up trapping code
that is not ready. then we make a buggy ISO, which we never update in the life
of the release. This leads first-time users of the ISO to not have a good
experience.
It's also annoying as a developer.
Please, let's discuss and be more organised.
Chris
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
