Re: The situation with version 0.4.14
Colin Finck <[email protected]> Mon, 15 Feb 2021 08:43:09 +0100
| Newsgroups | gmane.os.reactos.kernel |
|---|---|
| Message-ID | <[email protected]> |
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --===============4889202207059298956== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="50rECMEcP6NDnDA6vAJhSjYj0odDh90gA" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --50rECMEcP6NDnDA6vAJhSjYj0odDh90gA Content-Type: multipart/mixed; boundary="KMdTKwfsuugzTJc4mqqieMaQlMSbTYhOW"; protected-headers="v1" From: Colin Finck <[email protected]> To: [email protected] Message-ID: <b7d125c4-5551-44b5-bf5f-a47b4d27a30d-td3rRX5TIkhAfugRpC6u6w@public.gmane.org> Subject: Re: [ros-dev] The situation with version 0.4.14 References: <09dfc518bf9f7fe2bee72ad77f820cae974bd94f.camel-td3rRX5TIkhAfugRpC6u6w@public.gmane.org> In-Reply-To: <09dfc518bf9f7fe2bee72ad77f820cae974bd94f.camel-td3rRX5TIkhAfugRpC6u6w@public.gmane.org> --KMdTKwfsuugzTJc4mqqieMaQlMSbTYhOW Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Hey Victor, Thanks for bringing up that topic again. Indeed, it's really time for=20 0.4.14.. I want to get forward with the release, hence I tend to vote for 1. However, it's also wrong to just ignore Joachim's tremendous work in=20 compiling the list of regressions, and his valid concerns. Which is why I suggest a compromise: Let's come together next weekend=20 (20/21 February) and try to kill as many regressions as possible:=20 https://reactos.org/wiki/Tests_for_0.4.14#known_unfixed_regressions_in_de= scending_order_of_introduction It may or may not work, but then we have at least tried everything we=20 can as a volunteer-driven open-source project. Who else is going to join? Cheers, Colin Am 09.02.2021 um 16:47 schrieb Victor Perevertkin: > Hello! >=20 > It seems for me that it's time to bring up the topic about our RC > version - 0.4.14. >=20 > 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. >=20 > 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. >=20 > 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. >=20 > 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 :) >=20 > 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. >=20 > =3D=3D=3D >=20 > 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. >=20 >=20 > Cheers, > Victor >=20 >=20 > _______________________________________________ > Ros-dev mailing list > [email protected] > http://reactos.org/mailman/listinfo/ros-dev >=20 --KMdTKwfsuugzTJc4mqqieMaQlMSbTYhOW-- --50rECMEcP6NDnDA6vAJhSjYj0odDh90gA Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEENLXXTejc76VQ9g3AG6dOcEVroakFAmAqJg4FAwAAAAAACgkQG6dOcEVroama HA//ZMdydX8VfZ3yUkhlRxeh5cTWSYHORllI5tQoEMQqQooTYyP6U6pSm+z3mwaNCXpRYuT04u8L +g55/XwTJO6fMRmIsqtH2dcgCMGfSOjO4CcIHTGiAbEQaKoh+3tOoCDBfo0ExcffROa0qqqsYbWX t9QlZeXwkn0BZJ0f1BZP+UAMP2Jd2fMolPiOF0YdQvJZMf94qeBqFbEFGWcvxlAlD2Zfw/9of468 fDNgGW2Vtlijp7fU81JACSd48MIWoMFgEHJw3e1fS3sSXnrtRpGaqYptXw3MphRQSBKyTYPOL4Ja cf0BXAGCs5B5fe+zHXVYhmJmoXTW5FgF2ooRnCTBU4uJFc4tl5RmCR6lUkNcKnHy6EcBcfaM1n6i sp7s8zLYFx7p/UlL2X9KYlmvVqNZVRE8PsXIjzeLAiKx7AZXwo1vjGPNimXFzO8j1calOmAs2zQE Yt+x0+nDk6Ar2RH+TJyts1jqB92+IcKCuLujtNQc9LejOmVs64Z1t5HpagDKubxSkbAweQgrz56M wQPjAWrjg/nvVA7M3gws07mFimssJ5cDnbFCmV+YR7GnHGzuKylgwYb2Rkh+GYTmZfQx/2/M40fD 4K7s7rQw2reBWLnVCafb3PqtIJITjjBzQkTxAdQ46IIkjeXZ8MyIBt8RHuZirqlqlITgxjWYEjjw AUo= =swfe -----END PGP SIGNATURE----- --50rECMEcP6NDnDA6vAJhSjYj0odDh90gA-- --===============4889202207059298956== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Ros-dev mailing list [email protected] http://reactos.org/mailman/listinfo/ros-dev --===============4889202207059298956==--