Smuggler Archive
Thread: This is not a please read post.
CapnKate
Fri Jun 10, 2005 8:35 am
#14
Honestly, I didn't expect to see Smuggler in the patch notes-- Once I was downloading the patch, the story told itself.
The name of the big TRE files are patch_sku_2_17.tre, patch_sku_2_17_client.tre, and patch_sku_2_17_shared.tre.
Obviously, we're still in the Publish 17 cycle, and We were told "next publish". What's hit Test appears to be 17.2.
The name of the big TRE files are patch_sku_2_17.tre, patch_sku_2_17_client.tre, and patch_sku_2_17_shared.tre.
Obviously, we're still in the Publish 17 cycle, and We were told "next publish". What's hit Test appears to be 17.2.
Lubic
Fri Jun 10, 2005 8:57 am
#15
Well, from what i have read and heard, My best guesstimation would likely be mid-july for Publish 18. That is the Smuggler Publish my friends.
*disclaimer* This post in no way reflects anything said or posted by SOE,Lucasarts, or the Developers. It is purely speculation and I cannot be held liable for any repercussions pertaining to the release of said patch. /sarcasm off
HaughtyElf
Fri Jun 10, 2005 10:44 am
#18
MISTagent01 wrote:
/sigh
No comment.
/hands Veela a pie and a beer.
MISTagent01
Fri Jun 10, 2005 11:36 am
#19
Alpha_Bits wrote:
You can't win, Veela.
I know, that's why I decided not to share any more info that I garner with the community. It sucks, but if half the community can't trust me, why should I trust them? It makes sense to me, for the time being.
dlc3007
Fri Jun 10, 2005 11:45 am
#20
Veela,
I truly hope that you are responding to posts in this thread and not my original post. This was in no way directed at anyone outside the SOE offices. In fact, I was trying to word it as politely and constructively as possible.
I work in IT and everyone hates status reports. They serve an important purpose in my work place: they are used to update the clients on the progress of their requests. I was simply suggesting to SOE that a similar concept could be used for them to communicate to their clients: us.
If you (or anyone else) took this to be an attack or a demonstration of a "lack of trust", then we simply have a mis-understanding.
P.S. let's forget this whole thing and go derail the j3di forum.
Message Edited by dlc3007 on 06-10-2005 02:46 PM
HOTDOG
Fri Jun 10, 2005 11:56 am
#21
One time. At band camp. I had this tuba...
PIE!!
PIE PIE PIE!!
Hunh? What?....Oooooooooh, the JEDI forums....
sorry.
/burstrun
BladePride
Fri Jun 10, 2005 1:14 pm
#22
When you look at the list of professions for SWG, Smuggler jumps out yelling “Content”. But as it stands now it lays on its back whispering “Lacking Of”. I have been slowing working my way up the Smuggler tree and it’s getting about time that we see something that people have been talking about for 2 years. Plz let us know what’s going on. Just a bone or two and I will be happy.
VitoGenovese
Fri Jun 10, 2005 1:25 pm
#23
BladePride wrote:
When you look at the list of professions for SWG, Smuggler jumps out yelling “Content”. But as it stands now it lays on its back whispering “Lacking Of”. I have been slowing working my way up the Smuggler tree and it’s getting about time that we see something that people have been talking about for 2 years. Plz let us know what’s going on. Just a bone or two and I will be happy.
Oh we have been getting the bone brother, we have been getting it good, and hard for about 2 years. We just need to be "not boned" for a while.
Veela, I don't think anyone doubts you. I don't. We appreciate your information, and it gives us hope that there may be something to hope for! People are just noticing that the only time we get any good solid information is when one of us physically corners a dev. People are noticing that there is a HUGE disconnect between Players/Correspondents and devs. When people talked to the devs at fanfest about long standing problems that have been in Corr reports since the beginning of the program, the devs acted shocked. When they put up the Friday Feature about something saying how kickass it was and everyone responded that it have been broken for 6 months the TH acted shocked. There is a chasm between the makers of the product and the people that use it. As always Veela, you kick ass.
To the thread author: Titling a message "Tiggs/Developer please read" guarantees that there will be no response. They say that in the posting guidelines. I hope they decide to close the gap as much or more than anyone. But they will never read this thread unless someone gets abusive and the thread gets reported, Mr. Poopypants.
Its friday can I go home yet?
JFreeman
Fri Jun 10, 2005 1:27 pm
#24
The new slicing system is done.
Keep in mind, once a dev finishes a project like that, he checks it in.
It goes into our version control software ... and we have little
control over when it will get to you. Sometimes the developer isn't
even 100% sure which publish his change will be in: the next one, or
the one after that?
At that point, it's in for an upcoming publish with a lot of
other stuff. Any of that "other stuff" could delay the publish. Or we
could hear back from QA, "We don't have time to test that properly, so
let's hold it for the next publish and give ourselves time to test all
this other stuff." Or this could delay the publish itself. Or we could
discover other issues with it in testing that cause us to sit on it for
another publish, and so on. Really, anything could happen.
Most of the time, nothing bad happens, we haven't scheduled
anything that requires more QA time than QA can accommodate, and what
we check-in arrives on Live servers when it's supposed to. But this is
just not something we can promise, so we try not to do that.
This particular torpedo has left the tube, but we can't say when precisely it will make contact with the USS Smuggler.
"Soon".
Keep in mind, once a dev finishes a project like that, he checks it in.
It goes into our version control software ... and we have little
control over when it will get to you. Sometimes the developer isn't
even 100% sure which publish his change will be in: the next one, or
the one after that?
At that point, it's in for an upcoming publish with a lot of
other stuff. Any of that "other stuff" could delay the publish. Or we
could hear back from QA, "We don't have time to test that properly, so
let's hold it for the next publish and give ourselves time to test all
this other stuff." Or this could delay the publish itself. Or we could
discover other issues with it in testing that cause us to sit on it for
another publish, and so on. Really, anything could happen.
Most of the time, nothing bad happens, we haven't scheduled
anything that requires more QA time than QA can accommodate, and what
we check-in arrives on Live servers when it's supposed to. But this is
just not something we can promise, so we try not to do that.
This particular torpedo has left the tube, but we can't say when precisely it will make contact with the USS Smuggler.
"Soon".
VitoGenovese
Fri Jun 10, 2005 1:31 pm
#25
JFreeman wrote:
The new slicing system is done.
Keep in mind, once a dev finishes a project like that, he checks it in. It goes into our version control software ... and we have little control over when it will get to you. Sometimes the developer isn't even 100% sure which publish his change will be in: the next one, or the one after that?
At that point, it's in for an upcoming publish with a lot of other stuff. Any of that "other stuff" could delay the publish. Or we could hear back from QA, "We don't have time to test that properly, so let's hold it for the next publish and give ourselves time to test all this other stuff." Or this could delay the publish itself. Or we could discover other issues with it in testing that cause us to sit on it for another publish, and so on. Really, anything could happen.
Most of the time, nothing bad happens, we haven't scheduled anything that requires more QA time than QA can accommodate, and what we check-in arrives on Live servers when it's supposed to. But this is just not something we can promise, so we try not to do that.
This particular torpedo has left the tube, but we can't say when precisely it will make contact with the USS Smuggler.
"Soon".
Holy Hell I stand, happily, corrected.
Thanks Jfreeman!
Wait maybe it was that little bit of abuse at the end yah thats it...lol.
Ramsey_Lanclo
Fri Jun 10, 2005 1:32 pm
#26
JFreeman wrote:
The new slicing system is done.
Keep in mind, once a dev finishes a project like that, he checks it in. It goes into our version control software ... and we have little control over when it will get to you. Sometimes the developer isn't even 100% sure which publish his change will be in: the next one, or the one after that?
At that point, it's in for an upcoming publish with a lot of other stuff. Any of that "other stuff" could delay the publish. Or we could hear back from QA, "We don't have time to test that properly, so let's hold it for the next publish and give ourselves time to test all this other stuff." Or this could delay the publish itself. Or we could discover other issues with it in testing that cause us to sit on it for another publish, and so on. Really, anything could happen.
Most of the time, nothing bad happens, we haven't scheduled anything that requires more QA time than QA can accommodate, and what we check-in arrives on Live servers when it's supposed to. But this is just not something we can promise, so we try not to do that.
This particular torpedo has left the tube, but we can't say when precisely it will make contact with the USS Smuggler.
"Soon".
Fair enough... How about telling us _WHAT_ it is? There was an "In Concept" a couple months ago, but we've been told that it changed from that... How about letting us in on what's coming "soon"?