Closed Bug 554523 (bz-release-36) Opened 15 years ago Closed 14 years ago

Release Bugzilla 3.6

Categories

(Bugzilla :: Bugzilla-General, defect)

defect
Not set
blocker

Tracking

()

RESOLVED FIXED

People

(Reporter: mkanat, Assigned: mkanat)

References

(Blocks 1 open bug, )

Details

Attachments

(2 files)

It's looking like we won't need to do an rc2. I haven't seen too many critical bugs reported, and I don't see anything that we're checking in that will require extensive verification in another release.

  Primarily what I'm waiting on is all of the WebService QA tests to be done.

  LpSolit: Are there any Selenium tests that really *must* be complete before we release 3.6?
Flags: blocking3.6+
The list of bugs requiring Selenium scripts is:

https://bugzilla.mozilla.org/buglist.cgi?quicksearch=FIXED+testcase%3F

I didn't look at it recently, but new features should have a Selenium script before we release 3.6.
Okay. I'd like to release in about two weeks (April 6), so let me know which test cases you think are the most critical, and I may help out with them where I can.
I'm collecting quotes about the Extensions system to include in the release announcement and/or the release blog.

Here's one from timello:

"Bugzilla extensions really help me to do my customizations, giving me flexibility and reducing the impact in the tool's core. Congratulations Bugzilla team!" -Tiago Mello, IBM Linux Technology Center

I've also asked pyrzak for one.
Alias: bz-release-36
Depends on: 557385
Assignee: general → mkanat
Status: NEW → ASSIGNED
Attachment #438412 - Flags: review?(LpSolit)
Comment on attachment 438412 [details] [diff] [review]
Website Updates, v1

>Index: src/status/changes.html

> <table class="changelist">
> <tr><td><b>3.0 branch:</b></td></tr>
> <tr><td></td></tr>
>+<tr><td></td></tr>
> <tr><td><a href="[% PROCESS query f='2010-01-31+17:30' t='' %]">3.0.11 &rarr; today</a></td></tr>

In order to match what we did with older branches, we should have the following:

3.0 branch:
(branch closed)
3.0.11 -> 3.0.11+


Otherwise looks good. Good luck 3.6! r=LpSolit
Attachment #438412 - Flags: review?(LpSolit) → review+
Attachment #438669 - Flags: review?(LpSolit)
Bumped the version number for 3.6:

Committing to: bzr+ssh://bzr.mozilla.org/bugzilla/3.6/
modified Bugzilla/Constants.pm
modified docs/en/xml/Bugzilla-Guide.xml
Committed revision 7081.
Created Tags:
$VAR1 = {
          '3.6' => [
                     'BUGZILLA-3_6',
                     'BUGZILLA-3_6-STABLE',
                     'Bugzilla_Stable'
                   ]
        };

bugzilla-3.6         7081
  I've rolled the tarballs, but am holding off on releasing until tomorrow, as that is the planned release date that I've coordinated with Mozilla PR.
(In reply to comment #9)
>   I've rolled the tarballs, but am holding off on releasing until tomorrow

"tomorrow" as in "today"? I got you message at 7:23am this morning. :) Europeans are waiting for the 3.6 release already. ;)
Comment on attachment 438669 [details]
Release Announcement, v1

r=LpSolit
Attachment #438669 - Flags: review?(LpSolit) → review+
Thinking about the Download page, I think we should mention glob's Windows installers for 3.4.6 and 3.6 in a "Contributed installers" section. This would make it clear to everone that there are not officially supported by the Bugzilla team, but that this is a way to easily install Bugzilla on Windows, at least for testing and evaluation.
(In reply to comment #12)
> Thinking about the Download page, I think we should mention glob's Windows
> installers for 3.4.6 and 3.6 in a "Contributed installers" section. This would
> make it clear to everone that there are not officially supported by the
> Bugzilla team, but that this is a way to easily install Bugzilla on Windows, at
> least for testing and evaluation.

  Well, for now, we link to the Win32Install instructions, which link to the packages, so for this release I think we'll be OK. If glob is OK with your idea, though, I do like it and we'll do it for future releases.
> If glob is OK with your idea

/me is ok with this idea :)
Checked in the website updates.
Web site updated, release announcements sent.

I'll update FreshMeat later today.

I've already bumped the version number on the 3.6 branch to have a + on it.
bugzilla-update.xml updated.
(In reply to comment #16)
> I'll update FreshMeat later today.

which "today"? :)
Ohh, one of those todays or another. ;-D Hahaha. I guess it was THIS today.... :-D (FreshMeat update done, so this release bug can be closed.)
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: