Recommended Posts

only 10 days to go before we hit 1 June 2007, maybe they should think about renaming May release to June Release.

Patch Tuesday is June 12th, add a week for the AutoPatcher team to update AutoPatcher and test it thoroughly, making the June release due around June 19th.

Still plenty of time for the May release without fear of it being instantly replaced by the June one.

These silly displays of impatience help nobody.

I hope they don't go the bittorrent / 1 week laster http way. Ask the mirrors to trottle the downloads if get to high rather than giving HTTP up for a week.

In the past all download methods have been released at the same time. Comments like that really aren't necessary or appreciated. The AP Team has never done this in the past and knows that doing something like you mention would bring negative thoughts/comments from the users.

only 10 days to go before we hit 1 June 2007, maybe they should think about renaming May release to June Release.

Don't even joke about that! This has happened for the past 2 months in a row and none of us want to see that. I am honestly getting a bit impatient at the moment also, but COMPLETELY understand. No one knows what it is like to run a freeware project. It can be very stressful and time consuming. Freeware authors/contributors create software to help people and try their best to make all users happy. Sometimes "life" just happens and/or a big release is being compiled....so we cannot always get things done when users want us to. We just always trust that the users appreciate our hard work and understand.

You guys ought to stop using months to name the updates and just call them 2007-1, -2 etc and issue them when they are done.

That would stop the ungratefuls bitching about it when it takes longer than they want.

Keep up the great work - I am hanging out for the release - but happy you guys are doing your best - so when it is ready is good enough for me.

In regards to the naming structure:

January contains the updates released in January

February contains the updates released in February

March contains the updates released in March

Etc.

it's not to do with what actual month it's released in. (although I'd be pretty pointless to release one just before Patchday :p

i'm pleased to say that the prerequisite system is now complete, not much more to do at all now :D

Microsoft Security Advisory (927891)

Fix for Windows Installer (MSI)

Published: May 22, 2007

http://www.microsoft.com/technet/security/...ory/927891.mspx

http://support.microsoft.com/kb/927891

I'm not sayin nuttin..... but the lords of MS finally admit their installer breaks during MS Updates on some machines.

Thanks to the AP Team for keeping up the good work. I'm sure the new release will be everything our widdle hearts desire and then some. FAR BETTER to do a thing well... to do a thing right... than to push something out before it's time. Sincere thanks and best wishes.

BTW... Blaze... aka. Mr. Driving Newb.... I'm still gonna stay off the sidewalk

I think u just have to keep tight and bare a little more until SP3 is out.. then ap project would be much much more easier to maintain... i agree with idead to make it a june full if you need more time... remember it is better to test for 10 days then to test for 1 and learn u have to test it all over again

I think u just have to keep tight and bare a little more until SP3 is out.. then ap project would be much much more easier to maintain... i agree with idead to make it a june full if you need more time... remember it is better to test for 10 days then to test for 1 and learn u have to test it all over again

i agree totally

I also agree a june release would save rushing to get it out before the next patch day

While I agree that a rushed job is not such a good idea, it's been several months now since a release. To me at least, it seems that most of the new module is fairly mature and well tested and it has only been a couple issues that have been tough, and it seems to be fairly well ironed out.

If there is not enough confidence in AP 5.6, why not backport the fixes/updates to the old AP and release that, while continuing work on 5.6. I realise this means extra effort, but seems like a way to keep self pressure as well as screams of "are we there yet" at bay.

don't worry, i plan on having the new releases done by the weekend, i'm not waiting 18 days till the next patch tuesday.

Sounds like you are very confident that a 5.6 full May release will be good to go.... that's GREAT news!!!

Hey... I've got a couple or three new systems sitting around with nothing better to do... different makes / configurations... have de-crapified the ones OBE... one is a XP MCE 2005 w/no previous MS updates installed... others are clean XP SP2 Pro and Home installs from MS install disks... all are ready for roll out of AP 5.6 MAY... be glad to lock and load with the new release and let you know if any wheels come off of any. Also have a couple of systems in field w/ AP5.1 installed Feb release + MS Updates since... will check for conversion - upgrade issues. Probably won't find any issues because it sounds like you are being very thorough with the new release, and I will let you know how things go with the various configurations.

Just a note to everyone... BEFORE running AP... make sure you don't have any malware or other pre-existing registry goobly gook on your computer! These are the only issues I've encountered that will break AP and they are not the AP Team's responsibility. Refer to the other forums here and at MSFN to resolve any ad/spy/malware issues - clean registry - turn off programs that monitor / inhibit system changes... clean up previous failed update installer issues, etc. In other words, AP is NOT designed to FIX you computer but merely to install all the security patches and fixes that would normally occur through MS Updates. Again... if you start out with an unstable, buggered up system, then chances are that's what you'll still have after install/executing AP.

Thanks again AP Team!

Edited by cme4pc

I used AP during most of 2006, then stopped (break in IT arrangements) from about Nov till now. So I come back to download the latest update, to completely reinstall my main XP machine... and I find no updates at all since February.

So I read the thread and.......

|

|

|

|

|

|

|

|

v

v

..... I want to say a huge gesture of respect to Blaze and the crew, for their decision and handling. Obviously I'd have liked to be able to download the current updates right now, under the old script system, and if AP was bigger or a commercial venture that would be needed... but given the work involved and the communication (which makes SO much difference!), I will simply wait, smile and say "well done guys!"

I hope AP is out by the weekend as suggested. It certainly sounds close. And kudos to those who have waited patiently. Hope it's worth it, and ... look forward to the release!

Hi,

Can you remove the word "May" from the Autopatcher gui title?

In only 6 days most will think it's a month old!

I'd prefer the release number and revision, or nothing at all, just AutoPatcher.

According to my calculations you have 1 day to fix this!!

Hangin Out Big Time!

Kim

The name means which month's patches are included - obviously we can't call it June because the June patchday is weeks away. May will do just fine.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.