I'm proud to announce that the PortableApps.com Release Team has been selected. The Release Team will be helping move apps from Development Test to Pre-Release and from Pre-Release to Final by helping to ensure testing is done, compliance with PortableApps.com Format Specs, etc. After discussions among some developers and site admins, here's our team:
- BrianAll
- Chris Morgan
- Gizmokid2005
- Jacob Mastel
- OliverK
- Patrick Patience
- powerjuce
- Ryan McCue
- Taffin Foxcroft
- Zach Thibeau
All of your accounts have been set as Release Team members, so you have group access to edit the Development Releases Status page here:
https://portableapps.com/development/test/status
I've also setup a members-only mailing list just for team members so you can easily have quick discussions and ping each other regarding releases outside of the forums. Please drop me a note at the developers email on the Contact page with the email you'd like to use to subscribe. Put "Release Team" in the subject.
The status page isn't in the final format, and the first thing I'd like to do is get all the members on list and figure out what would be the easiest way to track it all on-page.
Everyone please congratulate the new team and let's thank them in advance for all the great work they're gonna put in to help us move releases along faster.
Best,
John
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Congratulations to all new release team members! ¡Buenas suerte a todos!
Na na na, come on!
Nice job guys
iLike Macs, iPwn, However you put it... Apple is better ^_^
"Claiming that your operating system is the best in the world because more people use it is like saying McDonalds makes the best food in the world..."
sweet, not lets give them some more apps to test
Lead, Follow, or get out of the way.
Uh oh.
I'm good with having a mailing list to which only members can post, but in the vein of transparency, public archives are a must. There's no real reason that we should have *anything* private. Yes, I mean *anything* including certain logs which are currently kept private from some people.
If you have valid arguments against this, I'd love to hear them, and as always, I'm willing to be convinced that they should be kept private, but I see no reason they shouldn't be publicly readable.
"If you're not part of the solution, you're part of the precipitate."
+1 with an extra comment.
This of course excludes business deals in which the partner has requested information remain confidential until the product is ready for release. If there's anything that can be shared, we'd all love to know though
The developer formerly known as ZGitRDun8705
I agree with Ryan on the mailing list, but if it does end up private it should be private for 3-7 days, and then it hits some form of archives.
But there’s no sense crying over every mistake,
You just keep on trying till you run out of cake.
That's the very, very least I'd be willing to use. If the logs aren't made public, I won't be using the list
Edit: That is, if I'm not convinced otherwise.
"If you're not part of the solution, you're part of the precipitate."
I agree with Ryan on this. There should be some type of public archive. Even if it's a delayed archive (3-7 days or something). I don't see any reason why there shouldn't be a public archive of the mailing list.
By private, I meant everyone and their grandmother can't post to it. Others can access the archives. Please don't assume.
Sometimes, the impossible can become possible, if you're awesome!
I was just clarifying, not assuming, and also stating points why it should be open, just in case.
On a side note, it might be a good idea to have a private mailing list for sensitive things.
"If you're not part of the solution, you're part of the precipitate."
That's what I figured you meant...and that's exactly what I mean. Makes perfect sense to me
thanks a bunch John, I'm looking forward to working on this with everyone else.
I'm currently in the process of cramming for this semester's final exams next week, and finishing up a final essay (which probably also explains why i'm awake at 2:45am), but on the bright side, I'm only in school for four hours total next week so i'll have plenty of time in my week off. Thanks! 
Cheers, Brian
Congrats Guys
I look forward to seeing the development test list chewed thru and will do what lil a Ubernoob like me can to help
PortableApps.com Advocate
Oh, and since you guys are Release Team members now, I take back all my criticism about your apps
They are all really really nice and should go official soon.
LOL
PortableApps.com Advocate
Say, your apps aren't so bad either...
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
hehe, I've copied and pasted from the best
This sounds great, John! Thanks for counting me in
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
means I wont see a big list of updates to to at the end of the dev test page and feel compelled to update it
Congrats all, look forward to seeing the benefits 
... to all of You
THX John.
Paid for Software more or less?
What You need is OSS!
Keep up the excellent work! Thanks again Zach for getting me off my lazy butt;-)
Np
anytime man
your friendly neighbourhood moderator Zach Thibeau
Nice to see some names to bug lmao. Look forward to working with you to get Blender Portable and one or two others moving up a level.
Dell XPS M1530 Laptop
Intel Core 2 Duo T9300 2.5GHz
4GB Ram
256MB GeForce 8600M GT
@John, email sent.
Too many lonely hearts in the real world
Too many bridges you can burn
Too many tables you can't turn
Don't wanna live my life in the real world
sent mine too.
Thanks guys for your willingness to do this,
for all your work in the past,
and for what you will do.
Tim
Things have got to get better, they can't get worse, or can they?
DITTO!
"What about Love?" - "Overrated. Biochemically no different than eating large quantities of chocolate." - Al Pacino in The Devils Advocate
Just a heads up, I can't edit the Dev Status or Test Releases page, I only have access the "View" and "Revisions" tabs.
Try again now.
Sometimes, the impossible can become possible, if you're awesome!
I still don't have access.
(Even after logging out and clearing everything out of the cache.)
just thought I would note that i dont have edit permissions either
But there’s no sense crying over every mistake,
You just keep on trying till you run out of cake.
My money is on the Full HTML input format permission not added to their accounts.
"If you're not part of the solution, you're part of the precipitate."
I think that was it. I was going nuts trying to figure it out.
Sometimes, the impossible can become possible, if you're awesome!
aha! I can edit it now. Thanks John.
But there’s no sense crying over every mistake,
You just keep on trying till you run out of cake.
Same here. Thanks.
I've made another possible layout example, that uses tables (similar to the dev test page). Any comments, suggestions? Lets decide what we want to do for the page layout.
I preferred the old way, just because it was easier to edit, this page is not meant to be an informative resource for those on the Release Team, so I think, it would work the way it was, where it is easy to add information.
That being said, I think there is a need for a table that you have added already. However rather than having the comments column we could have a "ready?" column which could be used to show which apps are ready to go, and which are not.
Regards
~powerjuce
Please search before posting. ~Thanks
Good idea, I thought it did seem like the comments were a little too much for one collum in the table.
I like the table layout, but I agree with Chris on changing APPDATA to Data. plus I thinks that the comments should stay in the layout that they're already in (separate from the table) to try and keep the table uncluttered. Please note this isn't saying that I'm anti-current format, I just want the end result able to be easily manageable.
on another note, whats with the javascript on the table? would it happen to be for the striping?
But there’s no sense crying over every mistake,
You just keep on trying till you run out of cake.
The script below is the old code for striping, and is no longer used. It might as well go. It might as well also go from development/test.
Oh yeah, I forgot to comment on here about my proposals - read the development/test/status page to find them
OK, I'll post it here:
I think that "APPDATA" shouldn't be a separate column, I reckon it should be just a "Data" column. Then inside the cell, have descriptive text, e.g. "APPDATA: redirected" or "APPDATA: moved at start and end, local backed up" or something like that. I wouldn't just use a "yes" or "no", I'd really just do it like Wikipedia does in its comparison tables; a background coloUr (I'm Australian :P) for the cell, red for fail, grey for unknown, green for pass or N/A. Maybe yellow if we think that there may be a better solution, e.g. an app may use one technique for APPDATA redirect, but another may be better. However, I would not do it the way they do with footnotes et al (e.g. "No[4]"), I would do it with putting the text in the cell. See the WP page "Comparison of integrated development environments" for a demonstration of the cell colouring technique. I think also a "License" column would be good, with the cell-background technique like on WP. Also, how about a "UPX" column? – Chris Morgan, 2009-02-02
Really, why is this a separate page from development/test? It seems to me it'd be a lot more convenient if we just added a few more columns to the development/test page, and put things in there. I don't think that the current permissions setup is in conflict with this page. – Chris Morgan, 2009-02-02
Can we get rid of the <script> element at the end of this page, which has obsolete code commented out in it? There doesn't seem much point in it, that's all... – Chris Morgan, 2009-02-02
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
it isn't aussies that use colour
Canadians do to 
same as favoUrite andyways the idea of a table with upx and stuff like that is a sound idea
your friendly neighbourhood moderator Zach Thibeau
On that note, what a pointless vowel to throw into those words. I make an effort not to use it.
I updated the table, and I also removed the javascript. I think that the current system that we have is good, as we have a quick way to see the status on apps, as well as detailed comments on each app.
Regards
~powerjuce
Please search before posting. ~Thanks
I just moved the discussion comments to the bottom of the page, and put the tables above the comments to organize the layout. Agreeing with Chris, i think the Registry and APPDATA columns should be merged, with a comment such as "copies to APPDATA" instead of just yes or no. Other than that, I think it's fine.
The combined table format in its current states isn't very efficient. We don't need the developer's name, just a link to the app itself (which will have it). If something like the OS column is designed to compatibility, how can we tell WHO tested it? The point of this is so that individual testers can sign off on what has been tested and by whom (accountability among testers). Which I think is more than a table will fit.
Perhaps we need a better list. Something like:
We could have the basic format and all items explained at the top. As well as a list of testers and their initials for easy reference. Plus a basic set of the items for new apps so people can copy and paste them in. Thoughts?
Sometimes, the impossible can become possible, if you're awesome!
Using the list for the detailed view for each app. However I feel that having a table will allow the testers to look at the page and get a quick glance at what needs to be done.
Rather than having the original idea how about this:
Application/Release OS PAF? Registry Data Recommendation Testers
on each part of the table they can put the initials and then put there names in the last slot. Then if you want to see the detailed version of what each tester thinks then can scroll down to see what the specifics of each decision.
Regards
~powerjuce
Please search before posting. ~Thanks
I've done a new attempt at a table that I think is more readable.
And we should have the JS striping in there.
Sometimes, the impossible can become possible, if you're awesome!
So has this just turned into "Battle of the Tables?" Chris had some ideas about merging the Development Tests and Status pages and adding 3 or 4 more columns to the Development Test tables (on development/test and development/test/status). personally, I dont think thats too good an idea as a fair few people go to that page to see if an app has been portablised, and if it has where it is. whereas the Release Status page has more details e.g. info about PAF compliance, anything left behind etc. so that the devs can fix them.
Now on to the development/test/status tables. John's table has a nice layout, but powerjuce's table has more info in it. if we had john's table combined with the comments area below, it shouldn't bee too hard to maintain. plus we can keep notes in the table, and if someone wants some more info about the testing that was done by SomeGuy they can refer to the comments below in order to find out more.
But there’s no sense crying over every mistake,
You just keep on trying till you run out of cake.
OS, PC, Data, PAF. I like it. OS for compatibility, PC for leaving stuff behind and ruining local stuff, Data for keeping its stuff, PAF for format compliance. Personally I reckon it'd be better then in a table.
How about the following structure in a table: |App|Author?|OS|PC|Data|PAF|
That way you could still have the background colours indicating bad/good/unknown/N/A (though you could do that in a list) and not have it messy. The table cells as you have now put them since I started typing this, need borders.
However, I reckon that the best way to do it would be to just make the dev/test page tables overflow a bit (which they currently have a conscientious objection to in most browsers) and stick on four more columns, OS, PC, Data and PAF. Maintainence would be so much easier then... and so of course I suddenly think of the potential problem of new releases
To be perfectly honest, I've often thought how much easier a lot of this would be if we used the Project module for Drupal... but it's not for Drupal 6 yet.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
by the way, shouldnt there be a link to status page on the Test Releases page?
PS: you didnt correctly spell my user name right on the "NVDA Portable" thing.
There will be once it's up and running. We're finalizing the layout and details at the moment.
Sometimes, the impossible can become possible, if you're awesome!
I'm assuming you've added (most of) us to the mailing list, but without an address, we can't post to it
"If you're not part of the solution, you're part of the precipitate."
Congrats All,
I've been wondering, what font is it that we use for the splash screens?
it's a commecial font that John has. I believe it's the same font that Mozilla uses for their logo's
your friendly neighbourhood moderator Zach Thibeau
Yesh. http://kb.mozillazine.org/Logo_fonts_for_Mozilla_projects
Problem is the price tag. I thought that it cost a grand, but I have "located" one for $44 USA. But I don't even know how that part will be working out.
Too many lonely hearts in the real world
Too many bridges you can burn
Too many tables you can't turn
Don't wanna live my life in the real world
The mailing list has been setup and all members should have received their welcome notice via email. We can all start using the list immediately. And let's start off by finalizing the setup of the Status page.
Non-members will be able to read archives on SourceForge.net here:
https://sourceforge.net/mailarchive/forum.php?forum_name=portableapps-re...
(nothing will show up at this moment though as it takes a couple hours to archive)
Sometimes, the impossible can become possible, if you're awesome!
#portableapps-rt has been set up for our use. Anyone can join the channel but the room is set to +m so no one but the rt will be allowed to speak. Patrick is setting up a logging bot that will have public logs. Anyone is allowed to idle and listen to us talk if they wish. All rt members have been +V'd already.
Release Team Member
Great, i'll add that to my auto-join.
Great News! Congrats guys!
Woo! Way to go guys!
Congratulations!
SWEET RAVE PARTY!
Congrats Folks, Having a great time testing and using the PortableApps you people have been posting and testing!!!
Will the status page be added to the development page or will I have to bookmark it?
If you're a dev, you only need to watch your own app thread as the bugs and PAF issues you need to handle will be reported there.
Sometimes, the impossible can become possible, if you're awesome!