I'd also vote for the 1st point and ultimately list the current regressions in the press release. After all the remaining regressions can be fixed and further regression testing be continued in the next release as usual. Most of the regressions which belong within user mode aren't huge stop-blockers so I see no point in delaying the release much.
Victor Perevertkin <victor.perevertkin(a)reactos.org> wrote on Tue, February 9th, 2021, 4:47 PM:
> Hello!
>
> It seems for me that it's time to bring up the topic about our RC
> version - 0.4.14.
>
> Our current "stable", 0.4.13 was branched on 30 September, 2019
> (remember those peacefull pre-COVID times :D)
> That's quite some time, but not the main issue I'd like to discuss.
>
> 0.4.14 was branched on 24 April, 2020. That's almost a year already.
> And we're in a difficult situation here - there are regressions, but
> nobody fixed them within this long time.
> According to https://reactos.org/wiki/Tests_for_0.4.14, there are 29
> unfixed regressions found for this release. I'd like to point out: most
> of them are among usermode and non-kernel/driver functionality, and as
> our development is mostly focused in the kernel right now, it's
> unexpected for them to be fixed unless a volunteer comes up.
>
> A quick reminder. Our "releases" mechanism is useful for finding
> regressions in the first place, there is no that much benefit for users
> here, because we're still a "deep" alpha. Correct me if I'm wrong.
> Joakim made a great job finding all regressions, and this work won't be
> lost in any case.
>
> We can't wait forever and I think it's time to resolve this situation
> somehow. I see two options:
> 1. Release 0.4.14 as-is. There were a lot more buggy releases, nobody
> dies from this.
> 2. Skip 0.4.14. This already happened once in the history of the
> project - 0.3.2 was skipped. I wasn't around at the time, but I may
> guess that reasons were similar to what we have today.
> (3.) Fix the bugs quickly. I don't expect this to happen, but who
> knows, maybe a volunteer appears :)
>
> Let's vote. This seem to be the only way for us to decide on things.
> Votes from the team members will be collected until 1 March.
>
> ===
>
> I personally vote for skipping the release. The work on finding
> regressions is already done, so the most important part of a release
> cycle for us is there (thanks Joakim!)
> If we do a release now, all the stuff we were writing in news reports
> for the last 6 month would be missing from it. That would cause (as I
> think) a lot of confusion to people. Moreover 0.4.14 is not that
> featureful release itself (compared to 0.4.13, which brought the new
> USB stack)
> So I suggest to move on and start checking 0.4.15 for regressions. I
> expect quite some of them to appear and we need time for fixing.
>
>
> Cheers,
> Victor
Whoa so many volunteers. ^^
Ok, I will note all down and then tomorrow check the limits we have. If one is not allowed to be added by me anymore I will still more than welcome everyone who wants to join the party. Maybe we even can add more on our own later. :D
Greetings
Daniel
Stas'M <binarymaster(a)mail.ru> schrieb am Sa, 20.02.2021 21:44:
> It seems Aleksey and Alexander are in, so it's going to be very interesting!
>
> Daniel, count me in :)
>
>
> --
> Stas'M was here
>
>
> Thursday, 18 February 2021, 12:54 +03:00 from "Daniel Reimer" <daniel.reimer(a)reactos.org>:
> > Not much to say. I paste a translated mail from CLT staff in here now to
> > give you all (non private) information we have by now:
> >
> > ...................
> >
> > As you can imagine, everything is a bit different this year. Due to the
> > Corona situation, we will not be able to meet at the TU Chemnitz in
> > March. Therefore, the Chemnitzer Linux-Tage 2021 will take place purely
> > virtually. With this mail we would like to inform you about the
> > essential boundary conditions.
> >
> > You can register additional booth attendants until February 21.
> > We will provide you with a virtual videoconference room in our open
> > source videoconferencing system BigBlueButton. Our visitors will be able
> > to enter this videoconference room during the event and interact with
> > you. We will offer demo dates for BigBlueButton. Until then you can test
> > it at the following URL:
> > https://demo.bigbluebutton.org/gl/
> >
> > You are free to decide about the design of your booth program. You can
> > either be available for talks and discussions the whole time or publish
> > a small booth program yourself (e.g. mini-discussion rounds, quizzes,
> > whatever comes to your mind). IMPORTANT: Please send us your booth
> > program (time, title, short description) by e-mail by February 21.
> > If you do not create your own program, please make sure that at least
> > one of you is always available in the video conference room during the
> > entire event, so that the booth does not look abandoned.
> >
> > ....................
> >
> > So I need one or two more guys to help out. Date is 13. / 14. March
> > 2021. If you wanna help out, I will need your full name, title if
> > existing and email address.
> >
> > HELP MEEE
> >
> > thx
> >
> > Daniel Reimer
> >
> >
> > _______________________________________________
> > Ros-dev mailing list
> > Ros-dev(a)reactos.org
> > http://reactos.org/mailman/listinfo/ros-dev
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
Not much to say. I paste a translated mail from CLT staff in here now to
give you all (non private) information we have by now:
...................
As you can imagine, everything is a bit different this year. Due to the
Corona situation, we will not be able to meet at the TU Chemnitz in
March. Therefore, the Chemnitzer Linux-Tage 2021 will take place purely
virtually. With this mail we would like to inform you about the
essential boundary conditions.
You can register additional booth attendants until February 21.
We will provide you with a virtual videoconference room in our open
source videoconferencing system BigBlueButton. Our visitors will be able
to enter this videoconference room during the event and interact with
you. We will offer demo dates for BigBlueButton. Until then you can test
it at the following URL:
https://demo.bigbluebutton.org/gl/
You are free to decide about the design of your booth program. You can
either be available for talks and discussions the whole time or publish
a small booth program yourself (e.g. mini-discussion rounds, quizzes,
whatever comes to your mind). IMPORTANT: Please send us your booth
program (time, title, short description) by e-mail by February 21.
If you do not create your own program, please make sure that at least
one of you is always available in the video conference room during the
entire event, so that the booth does not look abandoned.
....................
So I need one or two more guys to help out. Date is 13. / 14. March
2021. If you wanna help out, I will need your full name, title if
existing and email address.
HELP MEEE
thx
Daniel Reimer
Hello!
It seems for me that it's time to bring up the topic about our RC
version - 0.4.14.
Our current "stable", 0.4.13 was branched on 30 September, 2019
(remember those peacefull pre-COVID times :D)
That's quite some time, but not the main issue I'd like to discuss.
0.4.14 was branched on 24 April, 2020. That's almost a year already.
And we're in a difficult situation here - there are regressions, but
nobody fixed them within this long time.
According to https://reactos.org/wiki/Tests_for_0.4.14, there are 29
unfixed regressions found for this release. I'd like to point out: most
of them are among usermode and non-kernel/driver functionality, and as
our development is mostly focused in the kernel right now, it's
unexpected for them to be fixed unless a volunteer comes up.
A quick reminder. Our "releases" mechanism is useful for finding
regressions in the first place, there is no that much benefit for users
here, because we're still a "deep" alpha. Correct me if I'm wrong.
Joakim made a great job finding all regressions, and this work won't be
lost in any case.
We can't wait forever and I think it's time to resolve this situation
somehow. I see two options:
1. Release 0.4.14 as-is. There were a lot more buggy releases, nobody
dies from this.
2. Skip 0.4.14. This already happened once in the history of the
project - 0.3.2 was skipped. I wasn't around at the time, but I may
guess that reasons were similar to what we have today.
(3.) Fix the bugs quickly. I don't expect this to happen, but who
knows, maybe a volunteer appears :)
Let's vote. This seem to be the only way for us to decide on things.
Votes from the team members will be collected until 1 March.
===
I personally vote for skipping the release. The work on finding
regressions is already done, so the most important part of a release
cycle for us is there (thanks Joakim!)
If we do a release now, all the stuff we were writing in news reports
for the last 6 month would be missing from it. That would cause (as I
think) a lot of confusion to people. Moreover 0.4.14 is not that
featureful release itself (compared to 0.4.13, which brought the new
USB stack)
So I suggest to move on and start checking 0.4.15 for regressions. I
expect quite some of them to appear and we need time for fixing.
Cheers,
Victor
Hey Tom,
USB-Boot works with current nightlies and GPT is in the Works AFAIK(Hermes
should know more details).
Best Regards
Robert
Thomas Mueller <mueller6723(a)twc.com> schrieb am Mi., 10. Feb. 2021, 11:01:
> from Colin Finck:
>
> > This is not the kind of participation that has any place on the mailing
> list
> > of an open-source project.
> > Unsubscribed and blocked that person.
>
> > Colin
>
>
> > Am 09.02.2021 um 17:26 schrieb Dick:
>
> > > Hi,
> > > as a potential user this project makes me extremely tired. in 2000 or
> > > something like that i was excited because afvree windows replacement
> > > would be there...... it is 221!!! years later and there is...... still
> > > nothing, jst deep alpha as stated in last email. and 0.14 woudl have
> even
> > > regressions for 0.4.13. wouldnt it be more smart to finally build a
> > > timeline for this all? or to discuss the fact if this project makes any
> > > sense yet, it seems just a waste of time this way.
>
> First of all, I sent the wrong message a couple times, to ros-general.
> Now for the intended message:
>
> I have been idle with ReactOS because of no place to put it, and ReactOS's
> inability to boot from a USB stick.
>
> I can't install ReactOS on hard drive because of lack of GPT.
>
> I would need to be able to use ROSBE and write the result to a USB stick
> to boot, but don't think that is workable.
>
> Tom
>
>
> _______________________________________________
> Ros-dev mailing list
> Ros-dev(a)reactos.org
> http://reactos.org/mailman/listinfo/ros-dev
>
Hi all!
Our IServ system used for mail and mailinglists will be down for
maintenance on
THURSDAY, 4TH FEBRUARY 2021
15:00 ~ 17:00 UTC
During this time, you won't be able to send or receive any mails using
your @reactos.org address. Mail that is sent to an @reactos.org address
will usually be delivered later.
Other services won't be affected by this migration. In particular, all
means of communication through Mattermost or the website/forums will
stay live.
Best regards,
Colin Finck
