297791 - All instances of Bugzilla::Object should have ->create() and ->update() implemented

Status: NEW

(Bugzilla :: Administration, task)

Description

[Tiago Mello [:timello]]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050405 Firefox/1.0 (Ubuntu package 1.0.2)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050405 Firefox/1.0 (Ubuntu package 1.0.2)

Step 2: Write/Validation Functions
We need methods and/or subroutines for validations and database persistence.
All related routines about inserts, updates, deletes and validations for those
routines have to be implemented at this bug.

Reproducible: Always

Steps to Reproduce:

Comment 1

[Max Kanat-Alexander]

I think we should split validation and DB-persistence into separate bugs.

Comment 2

[Tiago Mello [:timello]]

Attachment: removed functions from 294160.

Comment 3

[Tiago Mello [:timello]]

Attachment: make_product_group routine.

This routine belongs to Product.pm.

Comment 4

[André Batosti]

Attachment: batosti_v1

an initial version.

Comment 5

[André Batosti]

Attachment: batosti_v2

more things for the Product.pm

Comment 6

[Frédéric Buclin]

bug 299753 should be fixed first, and objects should be used instead of old
code. This bug should not be a simple copy and paste from editproducts.cgi into
Product.pm.

Comment 7

[Frédéric Buclin]

Comment on attachment 195461 [details] [diff] [review]
batosti_v2

r- per my previous comment. And please remove the corresponding code from
editproducts.cgi (after the blocker is fixed).

Comment 8

[Frédéric Buclin]

The trunk is now frozen to prepare Bugzilla 2.22. Enhancement bugs are retargetted to 2.24.

Comment 9

[Frédéric Buclin]

We are in "soft freeze" mode to prepare 3.0 RC1.

Comment 10

[Max Kanat-Alexander]

Bugzilla 3.2 is now frozen. Only enhancements blocking 3.2 or specifically approved for 3.2 may be checked in to the 3.2 branch. If you would like to nominate your enhancement for Bugzilla 3.2, set the "blocking3.2" flag to "?", and either the target milestone will be changed back, or the blocking3.2 flag will be granted, if we will accept this enhancement for Bugzilla 3.2.

Comment 11

[Frédéric Buclin]

We are going to branch for Bugzilla 4.4 next week and this bug is too invasive or too risky to be accepted for 4.4 at this point. The target milestone is set to 5.0 which is our next major release.

I ask the assignee to reassign the bug to the default assignee if you don't plan to work on this bug in the near future, to make it clearer which bugs should be fixed by someone else on time for 5.0.