The Templates are compatible variable-wise, so you don't have to redo them.
The Database Schema also ahsn't changed.

I don't think that this is correct.
At least one table made a problem while upgrade 3.0.x to 3.5.
vBulletin is now using a table field which has the same name than the one AWS uses.

I tried an upgrade of my 3.0.8 board with AWS to vb 3.5 RC1 which brought up an error with a table. This was used from AWS and I had to delete it before the update went well.

I recommended weeks ago to change the AWS tables by adding them a prefix like
aws_
and the field names also
aws_

For future vB releases and other hacks I think this would be a good idea.

I was speaking of Templates :)

But you are right, there was a Field in Table userban (reason) that was previously used by AWS and is now a standard Field.

I am not a big fan of prefixes, therefore I most likely will not do so.

Ok but to make sure that vb 3.0.x AWS users can use AWS also in vb 3.5 the table must be renamed before upgrading.
Is AWS for 3.5 giving that field another name or how did you make it working KirbyDE?

This has been beaten to death. No, AWS does not care (during installation) if there is an error in the database, at least it didn't care at the AWS 3.4.x releases, I am not sure if this is true in AWS 3.5, KirbyDE can answer that to you, BUT:

AWS does not care if the "Reason" column is added by AWS installation script or if it already exists in the database. The column "reason" contains the reason why a person was banned. It's the same thing if this reason is added by AWS or by vB. Jelsoft finally decided that it is good to have the reason why someone was banned in the ban record, and added that column. So, there is no real conflict between AWS reason and vB reason, the column contains always the same thing. The reason a member was banned.

And please post your AWS 3.5 related questions in the appropriate thread.

Thank you.

@jluerken
As said, it doesn't really matter if AWS or vBulletin itself added the Field as it contains the same Data anyway.
AWS for 3.5 just uses the Field, it does not try to create or delete it, so there is no need to rename anything or such.

sv1cec, sorry if it's been beaten to death, I've been trying to follow (and have subscribed to) various threads that talk about AWS and more specifically how it will port to vb3.5, and this is one of a few threads regarding the matter that is updated daily. Since the questions I asked were not answered in the official 3.5.0b AWS release thread (at least not at the time I posted) I used this thread.

It's slightly confusing, but I thought a thread entitled "AWS and vb3.5" was an appropriate place to inquire about "AWS 3.5 related questions". I'll try not to let it happen again. better yet I will go and read through the thread I referenced above. I see it's up to 60+ posts since I went out of town last week, at that time it was only about 10 posts that did not address "upgrading".

Again guys, I can't say it enough, thank you all very kindly for your effort, and sorry about the misplaced questions. :)

Mutus123, I haven't answered to one of your posts. My answer quoted above, refered to jluerken who had asked the exact same thing here:

https://vborg.vbsupport.ru/showthread.php?t=92921

Also, support questions are not supposed to be here. They are supposed to be in the AWS 3.5 release thread, so that either me or KirbyDE know where to look for them. This thread was used only to inform members about the status of the porting.