Robinson Tryon píše v Po 15. 04. 2013 v 11:21 -0400:
BTW: ESC has had nothing against the one month after the last planned
release. If you update the wiki pages with the dates that would be cool.
Great! Pages are now updated. I think we're basically done with our
EOL Action Item now.
Robinson Tryon píše v Pá 12. 04. 2013 v 13:24 -0400:
On Fri, Apr 12, 2013 at 4:00 AM, Petr Mladek pmla...@suse.cz wrote:
Regarding the EOL date, I've mocked-up an example of how we could
display it on the wiki page:
On Mon, Apr 15, 2013 at 5:53 AM, Petr Mladek pmla...@suse.cz wrote:
Robinson Tryon píše v Pá 12. 04. 2013 v 13:24 -0400:
On Fri, Apr 12, 2013 at 4:00 AM, Petr Mladek pmla...@suse.cz wrote:
Regarding the EOL date, I've mocked-up an example of how we could
display it on the wiki page:
Robinson Tryon píše v Čt 11. 04. 2013 v 12:26 -0400:
On Thu, Apr 11, 2013 at 4:08 AM, Petr Mladek pmla...@suse.cz wrote:
Robinson Tryon píše v St 10. 04. 2013 v 11:29 -0400:
I think that only the single EOL date make sense. We do not provide
bugfix releases for bugfix releases. We provide
On Fri, Apr 12, 2013 at 4:00 AM, Petr Mladek pmla...@suse.cz wrote:
Taking the 3.6 branch as an example, the first release came out by Aug
12th., after which point there were no new major/minor builds until
4.0 was released just after 3.6.5 in February. That means that for 6
months, the 3.6
Robinson Tryon píše v St 10. 04. 2013 v 11:29 -0400:
On Wed, Apr 10, 2013 at 10:33 AM, Petr Mladek pmla...@suse.cz wrote:
I see that you both use a bit different logic, so we need to decide how
we count the 6 and 9 months. I understand it the following way:
+ the release is
On Thu, Apr 11, 2013 at 4:08 AM, Petr Mladek pmla...@suse.cz wrote:
Robinson Tryon píše v St 10. 04. 2013 v 11:29 -0400:
So would we provide an EOL date for each point release in a series, or
just a single EOL date for all of our 3.6.x released builds?
I think that only the single EOL date
Hi Robinson,
On Tue, 2013-04-09 at 19:52 -0400, Robinson Tryon wrote:
As Pedro mentioned, and as far as I understand it, our next step is to
pick an EOL date for each of our builds and then go update the wiki
pages. I'd be happy to help update the ReleaseNotes wiki pages, or to
ping pmladek
of this month?
Cheers,
Pedro
--
View this message in context:
http://nabble.documentfoundation.org/Libreoffice-qa-Lifecycle-of-builds-tp4048583p4048978.html
Sent from the QA mailing list archive at Nabble.com.
___
List Name: Libreoffice-qa mailing list
Mail
Pedro wrote:
Does this also mean that 3.4 versions can already be removed from the
bugzilla Version picker? And 3.5 versions after the 18th of this month?
Hi Pedro,
no, we can't. Version info in BZ should show where the bug appeared (or
at least has been observed the first time), also see
://nabble.documentfoundation.org/Libreoffice-qa-Lifecycle-of-builds-tp4048583p4049029.html
Sent from the QA mailing list archive at Nabble.com.
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change settings: http
Pedro schrieb:
The point here is that if a version is past the EOL and nobody will fix bugs
in that branch, there is no point in reporting bugs first observed in 3.4 or
3.5 (otherwise you should NOT remove 3.3 from the list either)
Hi Pedro,
you are completely wrong, I doubt that you read
On Wed, Apr 10, 2013 at 8:02 AM, Rainer Bielefeld
libreoff...@bielefeldundbuss.de wrote:
Pedro wrote:
Does this also mean that 3.4 versions can already be removed from the
bugzilla Version picker? And 3.5 versions after the 18th of this month?
Hi Pedro,
no, we can't. Version info in BZ
it makes more sense to advise the
user to update to a live branch and then to report the bug if it still
exists...
Regards,
Pedro
--
View this message in context:
http://nabble.documentfoundation.org/Libreoffice-qa-Lifecycle-of-builds-tp4048583p4049059.html
Sent from the QA mailing list archive
Michael Meeks píše v St 10. 04. 2013 v 10:25 +0100:
Hi Robinson,
On Tue, 2013-04-09 at 19:52 -0400, Robinson Tryon wrote:
As Pedro mentioned, and as far as I understand it, our next step is to
pick an EOL date for each of our builds and then go update the wiki
pages. I'd be happy to help
)
Regards,
Pedro
--
View this message in context:
http://nabble.documentfoundation.org/Libreoffice-qa-Lifecycle-of-builds-tp4048583p4049069.html
Sent from the QA mailing list archive at Nabble.com.
___
List Name: Libreoffice-qa mailing list
Mail
Robinson Tryon píše v St 10. 04. 2013 v 10:12 -0400:
On Wed, Apr 10, 2013 at 8:02 AM, Rainer Bielefeld
Rainer wrote:
So I believe we should mark the not-release-3.3 as inactive, what means
they will stay for the bugs where they are used, but can not be used for
new bug reports (except by the
On Wed, Apr 10, 2013 at 10:33 AM, Petr Mladek pmla...@suse.cz wrote:
I see that you both use a bit different logic, so we need to decide how
we count the 6 and 9 months. I understand it the following way:
+ the release is defined by the minor version release, e.g. 3.6
or 4.0
On Mon, 2013-04-08 at 09:05 -0700, Pedro wrote:
I think End of Life in that image doesn't mean the same as it does for
Microsoft software (or any other software I know)...
http://en.wikipedia.org/wiki/End-of-life_%28product%29
:-) and of course these versions can be supported, and
:
http://nabble.documentfoundation.org/Libreoffice-qa-Lifecycle-of-builds-tp4048583p4048810.html
Sent from the QA mailing list archive at Nabble.com.
___
List Name: Libreoffice-qa mailing list
Mail address: Libreoffice-qa@lists.freedesktop.org
Change
Hi *,
Am 09.04.2013 15:53, schrieb Pedro:
The image just needs to be corrected by user uroveits.
I´m uroveits. I've been watching this thread and I will change the
graphic when EOL has been set.
Regards
Jochen
___
List Name: Libreoffice-qa
On Tue, Apr 9, 2013 at 3:08 PM, Jochen oo...@jochenschiffers.de wrote:
Hi *,
Am 09.04.2013 15:53, schrieb Pedro:
The image just needs to be corrected by user uroveits.
I´m uroveits. I've been watching this thread and I will change the graphic
when EOL has been set.
:-)
Great.
As Pedro
On the ReleasePlan page[1] we have detailed descriptions of the
release dates of our builds, but I don't see any mention of the End of
Life (EOL) dates for the builds and branches, except for a small note
on the 'Lifecycle' graphic.
Do we have EOL dates in mind for our builds and branches? Is
at
AskLibO (or any other support channel) can tell people that the version x is
no longer supported and that they really need to update their software :)
Cheers,
Pedro
--
View this message in context:
http://nabble.documentfoundation.org/Libreoffice-qa-Lifecycle-of-builds-tp4048583p4048605.html
24 matches
Mail list logo
