What things are not in master already that you think might want to be in 2.9?
If it creates big changes or is complicated it should probably wait to the next 
release.
Or else we should wait (for release) till it's included and has stabilized 
(like 6 months)

If you think we are reasonably close to a release candidate then I think it 
would be better to
make the branch now and set a date. This would motivate people to finish loose 
ends and still allow master to except features without destabilzing 2.9.
We can always delay the date if we get a month out and find we need a bit more.
officially setting a date early is an important step we tend to miss.

Chris


________________________________
From: andy pugh <bodge...@gmail.com>
Sent: March 29, 2022 9:15 PM
To: EMC developers <emc-developers@lists.sourceforge.net>
Subject: [Emc-developers] Plan for 2.9 release

What do we think needs to be in 2.9? And when should it be released?

I think that the Python3 work might be reason enough. What is there
that isn't _quite_ right yet?

I am thinking that having the po4a documentation process working (but
not completed) would be nice. Then we can watch the online translated
docs grow.

Dewey's pluggable TP and homemod is a fun new feature.

We should probably pick a release manager.

--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912


_______________________________________________
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

Reply via email to