Forum:M&S: Second beta and launch coverage

From the RuneScape Wiki, the wiki for all things RuneScape
Jump to: navigation, search
Forums: Yew Grove > M&S: Second beta and launch coverage
Archive
This page or section is an archive.
Please do not edit the contents of this page.
This thread was archived on 26 November 2018 by JaydenKieran.

With the second Mining and Smithing beta, now referred to as the "second beta", coming in less than five days and the full launch of the rework less than two months away the issue of the coverage has come up once again. Though the "if" part of the question should be a self-explanatory "yes" and thus I will only address the "how" part here. The proposal is split in two parts: the beta and the launch, though there may be overlapping parts which I will explain below.

I) The second beta

Similar to the first beta, now referred to as the "technical beta", I think that the second beta should be covered in depth. However, I think that we should condense the coverage of the technical beta to only the pages that are exclusively tied to the technical beta, e.g. Decorated Doric, while all other pages and files are used as the ground work for the coverage of the second beta, and later the release. We should also either rewrite the mechanics listed on the main beta page it make it clear that these are now outdated
For the coverage of the second beta I propose that we update all of the pages that were added with the second beta while covering the updated and newly added mechanics to the main beta page, or simply link to the mechanics already covered on Suity's guide.

The alternative to that would be that we add something like (technical beta) to all the pages and files made in the technical beta and make new pages for the second beta and release. This would preserve the extent to which the first beta is currently covered, however this would also mean that we end up with essentially three pages with almost the same content.

In short I propose:

  • I) Update the already existing relevant pages from the technical beta and don't tie the newly made pages to the second beta.

II) The release of the rework

With the second beta we get the chance to prepare in detail for a high impact update and I am of the opinion that we should use this to ensure the best possible coverage on day one. While pages that are only affected in a smaller way,e.g. the quest rewards sections can be updated shortly before the update goes live other pages like the Mining and Smithing ones require a full rewrite. These pages should most likely be prepared in a Userspace and then be merged with the pages in the Mainspace on release day. If proposal I is accepted pages made during the beta periods could just be updated to the release version and then used.

In short I propose:

  • II) Prepare for the rework by making a separate version of high impact, high effort pages while use comments to prepare lesser impacted pages.

Discussion

Support both proposals - But if someone has a better/different idea, then by all means go ahead and start a discussion. Srylius (talk) 15:57, 9 November 2018 (UTC)

Support One(Sorta) Support Two - I am in complete agreement however, I think there is something to be said about keeping all of the beta information clearly labeled "1st beta, technical beta, etc." However, I think these could ultimately be combined into one page explaining the mechanics and changes once the release happens. Upon release, there is definitely going to need organization and many different people coordinating together so that we can be the first source with the most accurate information. Addendum to your proposal? Perhaps create a 'Major Release' team? And have them organize themselves in a way that way major pages can be changed almost immediately and lesser pages are updated during release day as information rolls in? RuneMetrics icon.png Tyler JarretTalkLight animica.png 16:07, 9 November 2018 (UTC)

I Support the idea of a Major Release Team. Sounds like a great idea, especially if the team members have already been helping out from the start. They will know the most of each change already. MissLioness (talk) 09:53, 10 November 2018 (UTC)
I, too, support a Major Release Team (though naturally other people not on the team can contribute, obviously!) , and both proposals as well. 7kyt1iT.gif --WINE OF GOOD HEALTH (Actually Stinko) 19:39, 10 November 2018 (UTC)

Comment - I'm assuming the plan is to have a Beta subsection for currently in-game content like rune bars or a subpage to then later merge to the main article. I see nothing wrong with creating more beta content pages as long as it is clearly indicated with a template that it is part of the beta. I support the proposal. - Ryan PM 20:45, 9 November 2018 (UTC)

Support both proposals - Though I wonder whether it is easier to move pages from the technical beta pages to the Mainspace, or if Userspace is more friendly for that? All in all, I support any notion that would allow us to have the changes up at launch. MissLioness (talk) 09:53, 10 November 2018 (UTC)

Support - preparing as much as you can in advance is always good :) There are already pages in existence from the previous beta with a template that you can use to indicate that the content is only available in beta. I would be in favour of uploading over images from the previous beta and keeping the content from both betas on the same pages, though you can always explain any major changes that occurred between the two betas (and later the release) on the pages. Are there any significant changes i.e. content that is now scrapped or completely new ideas? If there are new items it would be worth asking User:Gaz Lloyd for help as it would appear he created skeleton pages for all the beta's items last time using his bot.

For changes to existing pages you could create versions in your userspace and then copy over the rewritten version once the rework goes live (either by copying the pages' contents to a new page or by actually moving the page into the mainspace). Smaller changes can also be made to the actual pages using comments, which aren't visible to readers, so long as you remember to remove the comment tags afterwards :P (<!-- comment -->)

I'm glad there are enough people enthusiastic about the update to warrant a special release team (I know I've certainly lost patience and interest in the rework by this point). If you want to co-ordinate the work on the update a discord channel for Mining and Smithing in #projects might be helpful? Magic logs detail.pngIsobelJTalk page 10:14, 11 November 2018 (UTC)

Support - I think it'd be interesting to see what has changed from technical beta to second beta to final release, maybe that can be put somewhere on respective pages? As for images, I think uploading over existing ones are fine. I don't really think a "team" is necessary, but gaz created a channel in discord so all M&S discussion can be focused and documented there. Talk to Kelsey 15:37, 11 November 2018 (UTC)

Comment - The plan would be to create a history section for the rework (probably even for stuff we know of before the current iteration) with triva sections on the respective subpages. Srylius (talk) 15:53, 11 November 2018 (UTC)

Comment - I have created a custom namespace called Beta and a page outlining how it should work on User:JaydenKieran/M&S. jayden 21:30, 11 November 2018 (UTC)

Closed - The above implementation is in full effect already, no need to keep this open any longer jayden 02:40, 26 November 2018 (UTC)