0.3.11 September
Moderator: Moderator Team
0.3.11 September
As I thought, it's not out yet and the homepage needs updating. The plan was to stop all crashes in testman right? at least 10 tests seem to have just been cancelled. Why not just go for the text in the new firefox displaying correctly for 0.3.11 and make stopping about 5 crashes with each new release? If it's really the plan to stop all crashes before 0.4 it looks like there will be many more 0.3.x releases.
Re: 0.3.11 September
uhm ... you know the meaning of "earliest projected release date" ?dark wrote:As I thought, it's not out yet and the homepage needs updating.
Re: 0.3.11 September
Is requesting one word to be changed heresy? That still doesn't answer the question of the releasing when all testman tests don't crash issue, there are much more crashes and cancellations than when I looked at it 1 or 2 months ago.hefner wrote:uhm ... you know the meaning of "earliest projected release date" ?dark wrote:As I thought, it's not out yet and the homepage needs updating.
Re: 0.3.11 September
I think the biggest problem is, if someone keeps updating that date people expect it to be accurate. If it's not out this month, someone will be expected to update it again.
As it is, it indicates that the goal was September. Being October, it also indicates that something is holding it up. I think that's the most clear message we can send.
The problem now is there is no commitment date, so no one would know which month to put as the new target month. It's done when it's done.
As it is, it indicates that the goal was September. Being October, it also indicates that something is holding it up. I think that's the most clear message we can send.
The problem now is there is no commitment date, so no one would know which month to put as the new target month. It's done when it's done.
-
- Test Team
- Posts: 802
- Joined: Thu Apr 03, 2008 2:17 pm
- Contact:
Re: 0.3.11 September
No. There's no point updating the -earliest- projected date. If it's set in the future and it lapses, tough.dark wrote:As I thought, it's not out yet and the homepage needs updating.
Re: 0.3.11 September
It is planned to release every two months a new version of ReactOS but it is not a fixed release period.
-
- Posts: 133
- Joined: Sun Aug 30, 2009 4:42 pm
Re: 0.3.11 September
EmuandCo or hto - Please Just Lock This Thread, People Need to understand that releases will be published when they are ready, not when they start wining about though their own ignorance toward ReactOS.
Wesley Howard
ROS Contributor - Web Developer
ROS Contributor - Web Developer
Re: 0.3.11 September
It's not like we don't have SVN anyway, setting up VirtualBox and ReactOS SVN in it isn't rocket science.
Re: 0.3.11 September
Seconded...livestrong2109 wrote:EmuandCo or hto - Please Just Lock This Thread,
Re: 0.3.11 September
We don't lock threads unless they violate the code of conduct. So far I have not seen any, but the snarky comments by responders are approaching.
Re: 0.3.11 September
Just a suggestion...
Since you know when ROS is ready to a new release, why don't you put progress bar instead the roadmap? That same progress bar could be linked to SVN for instance...
BR
Cutty
Since you know when ROS is ready to a new release, why don't you put progress bar instead the roadmap? That same progress bar could be linked to SVN for instance...
BR
Cutty
Re: 0.3.11 September
I think it depends on the testers, we need to open a test page again and post critical bug reports to get a good map on what is fixed and still open based on the roadmap.
ATM FF 2.0.xx, Seamonkey 1.1.18/19, newest Putty, latest AbiWord and misc install programs work leaving some menu toolbar drawing issues.
ATM FF 2.0.xx, Seamonkey 1.1.18/19, newest Putty, latest AbiWord and misc install programs work leaving some menu toolbar drawing issues.
Re: 0.3.11 September
Except that the roadmap is completely out of date despite efforts to get it updated since developer feedback on objectives have been nonexistent.
And how would you propose we decide whether to increment the progress bar?cuttysark wrote:Just a suggestion...
Since you know when ROS is ready to a new release, why don't you put progress bar instead the roadmap? That same progress bar could be linked to SVN for instance...
BR
Cutty
I know how. :)Z98 wrote: And how would you propose we decide whether to increment the progress bar?
If there's no any strict mathematical method, then we shall allow our intuition to guide us.
Let the right side will symbolize the unattainable "ideal state" of things. Any developer, when feels that the project has made some progress, can increment the bar; how often to do it and how much to increment, is completely up to a developer. It can reflect either an individual or a collective opinion.
There can be some ticks, numbers, inscriptions, under the bar. When it approaches the right side, it should be scaled (zoomed in), so visually, but not conceptually, it moves back.
Re: 0.3.11 September
I dunno. By the milestones in the bugzilla?
Thats what i go off .
Though I don't think it matters at the moment. No ones hanging out for the next official release. Which still won't install on 90% of pcs. At the moment it is good for a vm and satisfy public curiosity.
If it becomes usable. It might be relevant to have better tracking. But so far I think I know everyone who frequents the site by forum. It's not too often that a new name pops up and stays around.
Thats what i go off .
Though I don't think it matters at the moment. No ones hanging out for the next official release. Which still won't install on 90% of pcs. At the moment it is good for a vm and satisfy public curiosity.
If it becomes usable. It might be relevant to have better tracking. But so far I think I know everyone who frequents the site by forum. It's not too often that a new name pops up and stays around.
Who is online
Users browsing this forum: Bing [Bot], DotBot [Crawler], Google [Bot], Yandex [Bot] and 1 guest