Topic: Has anyone had a software update in the last 2 weeks?

[NomadOfNorad]

I have not seen any updates show up on the Software Installer screen of the SME Server Manager web-interface, even though I have "Check for updates daily" Enabled, and even though I am reasonably sure there have been software updates created within those two weeks.  Ones related to Bugzilla bug #1081, at least.

Maybe I'm just being paranoid and there genuinely have NOT been any available updates since two weeks ago.   Have there been any updates?  Received by the users, or put in place by the programmers?  Or is it normal for there to be a longish lag time (say, two or three weeks) between when a bug is reported as Resolved and a bug-fix created, and when the bug-fix actually gets propogated to the end users...?

I don't want to post a bugreport about a bug-that-isn't-really-there, afterall... but if it is comfirmed from others here that I'm NOT imagining things, I will post a bug-report forthwith.

[psoren]

I have not seen any updates show up on the Software Installer screen of the SME Server Manager web-interface, even though I have "Check for updates daily" Enabled, and even though I am reasonably sure there have been software updates created within those two weeks.  Ones related to Bugzilla bug #1081, at least.

Maybe I'm just being paranoid and there genuinely have NOT been any available updates since two weeks ago.   Have there been any updates?  Received by the users, or put in place by the programmers?  Or is it normal for there to be a longish lag time (say, two or three weeks) between when a bug is reported as Resolved and a bug-fix created, and when the bug-fix actually gets propogated to the end users...?

I don't want to post a bugreport about a bug-that-isn't-really-there, afterall... but if it is comfirmed from others here that I'm NOT imagining things, I will post a bug-report forthwith.

Hi,

If you're on 7RC! then i don't think there has been any.

Per

[NomadOfNorad]

Okay, well I'm looking at Bug Report 1081 (http://bugs.contribs.org/show_bug.cgi?id=1081) I see

------- Comment #3 From Gordon Rowell 2006-03-27 20:45 [reply] -------

* Fri Mar 24 2006 Charlie Brady <charlie_brady@mitel.com> 1.4.0-03
- Ensure that imaps is started or stopped if required, during
  email-update event. [SME: 1125]

* Sun Mar 19 2006 Charlie Brady <charlie_brady@mitel.com> 1.4.0-02
- Fix per IP concurrency control. [SME: 1081]


Built.


------- Comment #2 From Charlie Brady 2006-03-19 11:44 [reply] -------

Thanks Michael. Patch is committed to CVS.

...which I assume means that a bug-fixed version of the affected program or programs should be sitting somewhere waiting to be downloaded.  Is there routinely a week or more delay between completion of a new version of a given program and it showing up in Software Installer?

--addendum:
And yeah, I'm running version 7.0rc1

[pfloor]

Bugs are fixed one at a time.  All fixed bugs go to a builds area and will be put into rc2 and then released all at once.  There is a very good reason for this. Just yesterday a package was put into the rc2 "work in progress" and then pulled because it broke the server.  We don't want to release anything that will break the server at this point.

Testers get different versions of the releases as they go along (you only see the last one).  We test and re-test and end up spending a lot of time correcting errors, updating and even re-loading quite often.  We don't want this to happen to the general public so we wait and release all tested update at once.

rc2 is close...be patient!  When released, you will see updates available in your server-manager or via "yum update" from the CL.

Paul

[NomadOfNorad]

Ah, goodygoody.

Uhhmmm...  Shouldn't this delay-before-release process be mentioned somewhere in the FAQ or something, though?  Might stop people like me from worrying so much...  

Anyway, keep up the good work.

[pfloor]

The time between releases is highly unpredictable.  For instance, pre1 to pre2 (almost released then quickly pulled) to pre3 to pre4 happened fairly fast.  Lots of small and a few big fixes.

rc's will take a lot longer to evaluate as they are candidates for release and need extensive testing (and more testers please!!!).

Can you help over at the bug tracker?  Any help would be highly appreciated and help us get closer to that final goal!!!

P.S. I keep saying "We" and "Us" and in all reality I am not one of the developers.  As a matter of fact I know very little about Linux and even less about coding.  I just decided to give some of my time back to a project that has saved me a ton of money over the years so I dove in and have actually diagnosed several bugs and gave the developers the direction needed to fix those bugs.   I haven't fixed any bugs myself but I have saved the developers a few precious hours and that’s what really counts.  You don't have to fix the bugs to help.  The developers can't possibly test every situation so report any bugs you find and just follow their instructions so they can figure out what is wrong.

After a while, you start to feel like part of the team and start using terms like "we" and "us" when in fact it is "them" that I am really talking about.


As a side effect I HAVE learned very much from this process and even more from the developers themselves.  Thanks to them I am a better (and smarter) person.

Paul

[NomadOfNorad]

The time between releases is highly unpredictable.  For instance, pre1 to pre2 (almost released then quickly pulled) to pre3 to pre4 happened fairly fast.  Lots of small and a few big fixes.

Well, just stating in the FAQ that "sometimes they have to hold out a new version for awhile to bug-check..." would be more than enough.  No need to specify an interval.  

rc's will take a lot longer to evaluate as they are candidates for release and need extensive testing (and more testers please!!!).

Can you help over at the bug tracker?  Any help would be highly appreciated and help us get closer to that final goal!!!

I suppose I could poke around on there occasionally at least...

P.S. I keep saying "We" and "Us" and in all reality I am not one of the developers.  As a matter of fact I know very little about Linux and even less about coding.  I just decided to give some of my time back to a project that has saved me a ton of money over the years so I dove in and have actually diagnosed several bugs and gave the developers the direction needed to fix those bugs.   I haven't fixed any bugs myself but I have saved the developers a few precious hours and that’s what really counts.  You don't have to fix the bugs to help.  The developers can't possibly test every situation so report any bugs you find and just follow their instructions so they can figure out what is wrong.

After a while, you start to feel like part of the team and start using terms like "we" and "us" when in fact it is "them" that I am really talking about.

Well, as long as "them" doesn't turn out to be a bunch of giant ants!  

[Old sci-fi movie reference...]

I'll think about it, anyway...  

As a side effect I HAVE learned very much from this process and even more from the developers themselves.  Thanks to them I am a better (and smarter) person.

Paul

[pfloor]

Well, just stating in the FAQ that "sometimes they have to hold out a new version for awhile to bug-check..." would be more than enough. No need to specify an interval.

Well no, it's not really needed.  This is just how all open source software development is done.  You either get involved to help speed it up OR....

You wait patiently until it's done.

Paul

[NomadOfNorad]

So, is there a Bugzilla report, or something, that I can follow along in to see when the next system-update comes out?  That is, to get an idea when I'll see the updates show up on the Software Installer screen?  Or is that sort of thing handled outside of Bugzilla?

[pfloor]

It's the very first thread in this forum:

http://forums.contribs.org/index.php?topic=31011.0

Any official release news is in that thread.  Go to it and click "Watch this topic" at the bottom and you will get an email when there is any new news.

It's that easy!

If you are looking for a timeline or roadmap then you will be searching forever.  As stated here many, many times:

"We do not provide a roadmap or timeline...It will be done when it's done"

[NomadOfNorad]

It's the very first thread in this forum:

http://forums.contribs.org/index.php?topic=31011.0

So this will tell me when rc2 is officially out, eh?

Any official release news is in that thread.  Go to it and click "Watch this topic" at the bottom and you will get an email when there is any new news.

It's that easy!

Done.

I guess I was expecting a thread somewhere where the individual programmers working on the update were discussing the update, describing what had been done and not done, and the results thereof... so I could be a fly on the wall.

Presumably that must be a closed forum, though, or something.

If you are looking for a timeline or roadmap then you will be searching forever.  As stated here many, many times:

"We do not provide a roadmap or timeline...It will be done when it's done"

No, just looking for something where I could observe the progress being made, as it happens.  No such animal, eh?

[pfloor]

It's called the bug tracker, open to everyone.  There are 1230 bugs in total...Start reading and you will discover everything you are asking for.  Every bug contains Who opened the bug, what was done to fix it (or not fix it), what the new package version is, etc...  The link is on the left (where it has always been).

All open pugs for SME7 are here

http://bugs.contribs.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=SME+Server+Release+7.0&content=

Search all bugs here:

http://bugs.contribs.org/query.cgi

You can also join a couple of mailing lists here:

http://no.longer.valid/phpwiki/index.php?Mailing%20Lists

There are no hidden or private lists, fora, bug trackers, etc...All the information you are wanting is here in one place or another.

All you have to do is look and read.

[NomadOfNorad]

It's called the bug tracker, open to everyone.  There are 1230 bugs in total...Start reading and you will discover everything you are asking for.  Every bug contains Who opened the bug, what was done to fix it (or not fix it), what the new package version is, etc...  The link is on the left (where it has always been).

All open pugs for SME7 are here

http://bugs.contribs.org/buglist.cgi?query_format=specific&order=relevance+desc&bug_status=__open__&product=SME+Server+Release+7.0&content=

Ah, thankee....  I have saved-to-desktop the above URL and will consult it regularly.

Search all bugs here:

http://bugs.contribs.org/query.cgi

You can also join a couple of mailing lists here:

http://no.longer.valid/phpwiki/index.php?Mailing%20Lists

Will probably also poke around in the lists' archives...

There are no hidden or private lists, fora, bug trackers, etc...All the information you are wanting is here in one place or another.

All you have to do is look and read.

Thank you for your help and patience.  You've been a blessing.