The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
#1
|
|||
|
|||
![]()
What is the process for moving items from Beta to Full Releases?
Do you ask the person who posted the hack? Do you arbitrarily move it over after 1 person says it works for them? How could this process be improved? Beta Hacks and Full Releases should never intermingle IMO. Items which are Beta and promoted to Full Releases should have new threads created instead of having them just moved over. There are occurances of pages and pages of debug stuff leftover from Beta stages. There are other occurances of what are clearly still Beta hacks moved right into Full Releases, often with Authors who are not around to support the numerous people seeking help with the nonfunctional hack. I think some improvement here could go a long way in the quality of hacks in the full releases section. |
#2
|
||||
|
||||
![]() Quote:
![]() |
#3
|
||||
|
||||
![]()
Matthew is absolutelly right
|
#4
|
|||
|
|||
![]()
Do any of them get moved without the authors control?
|
#5
|
||||
|
||||
![]()
nope
|
#6
|
||||
|
||||
![]() Quote:
If people look at a hack, and see 5 pages of people having serious problems with it... regardless of if they are fixed or not they will be far less inclined to install. Why not jsut have a link that says 'Final' along with the other hack editing options. When you click it, it copies first post to the corresponding Final Release forum, and closes the beat thread (with a nice little message and link informing users that the hack has gone final). Ya, sounds like a pain... but could be fun ![]() Just my 2 cents. |
![]() |
Thread Tools | |
Display Modes | |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|