Re: Status Meeting (November 2018)
Dick <[email protected]> Wed, 28 Nov 2018 19:35:49 +0100 (CET)
| Newsgroups | gmane.os.reactos.kernel |
|---|---|
| Message-ID | <[email protected]> |
It is common use to start beta from 0.5 because it is half way up to 1.0. bringing 0.5 as alpha willl cause much disappointment and is confusing for users. I think an interesting point to talk about would be a roadmap. when can average users start to use reactos as their daily os? Is reactos able to become usable as windows-alternative before windows is gone and forgotten? On Wed, 28 Nov 2018, David Quintana (gigaherz) wrote: > I agree on "beta" being more like 80-90% implementation coverage, however > given the 80/20 rule applied to development, that says that < 20% of the > bugs cause >80% of the bug reports (I'd guess this will be 5% of the bugs > causing 95% of the reports, if not even more), so one could argue that > having a codebase 80% complete, is still only 50% of the work, because the > other 50% will be a whole lot of polishing. > > On Wed, 28 Nov 2018 at 18:03, Ged Murphy <[email protected]> > wrote: > > The link between 0.5 and beta was an old statement we used to > have on our website, I’m not sure why that relationship existed > other than a splitting an integer in half and assigning 0.5 to > each stage. > > I’m more of the opinion that beta products are close to release, > so 0.8+ would be more suitable. > > > > Anyway, it’s a conversation to be had internally. > > > > Ged. > > > > From: Ros-dev <[email protected]> On Behalf Of > [email protected] > Sent: Wednesday, 28 November 2018 16:51 > To: ReactOS Development List <[email protected]> > Subject: Re: [ros-dev] Status Meeting (November 2018) > > > > Hi! > > Usually when we talk about ReactOS 0.5, we implicitly think that > it will enter beta state there. > So unless you consider this to not completely hold anymore, we > can look at what remains to be done/fixed (importantly) so that > we may qualify as going into beta state. > (And yes, USB and storage sound strongly as prerequisites for > 0.5 in my opinion). > > Best, > Hermes > > De : "Ged Murphy" > A : "'ReactOS Development List'" > Envoyé: mercredi 28 novembre 2018 17:42 > Objet : Re: [ros-dev] Status Meeting (November 2018) > > > Some potential talking points: > > > > o Selecting a new coordinator > o Version bump to 0.5 > o USB / Storage (perhaps linked to a 0.5 release) > o Mattermost > o New website progress > > > > > > From: Ros-dev <[email protected]> On Behalf Of Mark > Jansen > Sent: Wednesday, 28 November 2018 16:13 > To: ReactOS Development List <[email protected]> > Subject: Re: [ros-dev] Status Meeting (November 2018) > > > > We can discuss this if you are present, but I don't see the > value in discussing it without you. > > We have seen before that something discussed without the initiator > being present is time not well spent, since it is a bit hard to argue > with only one side of the argument present > > > > > > > > Op 26 nov. 2018 12:15 schreef [email protected]: > > Hello, > > I may not be available as it's the day when I'm going > somewhere for a conference; it just depends at which time > I arrive at destination. > > For the meeting we may talk about the best way we can move > to delivering all-in-one ReactOS ISOs (containing livecd + > installation in both text and GUI modes), and which > changes this could imply for our infrastructure > (buildbots/website...). > > Best regards, > Hermes > > De : "Javier Agustìn Fernàndez Arroyo" > A : "ReactOS Development List" > Envoyé: samedi 24 novembre 2018 22:06 > Objet : Re: [ros-dev] Status Meeting (November 2018) > > > I'm at work but I will do my best to attend! > > > > El sáb., 24 nov. 2018 21:38, Colin Finck <[email protected]> > escribió: > > Hi all! > > Let me invite you to the November 2018 meeting, > taking place next > Thursday, November 29, 2018 at 19:00 UTC. > Invited members will again receive their credentials > shortly before the > meeting. > > This will be the first meeting since August and I > hope we get some more > topics than just the obligatory Status Reports. > Please send your > proposals by replying to this mail. > > > Best regards, > > Colin > > _______________________________________________ > Ros-dev mailing list > [email protected] > http://reactos.org/mailman/listinfo/ros-dev > > > > > _______________________________________________ > Ros-dev mailing list > [email protected] > http://reactos.org/mailman/listinfo/ros-dev > > > > > > > > > _______________________________________________ > Ros-dev mailing list > [email protected] > http://reactos.org/mailman/listinfo/ros-dev > > > > _______________________________________________ > Ros-dev mailing list > [email protected] > http://reactos.org/mailman/listinfo/ros-dev > > > _______________________________________________ Ros-dev mailing list [email protected] http://reactos.org/mailman/listinfo/ros-dev