Investigate a tamarin-redux-stable repository

NEW
Unassigned

Status

Tamarin
Build Config
--
enhancement
8 years ago
7 years ago

People

(Reporter: Edwin Smith, Unassigned)

Tracking

unspecified
Future
Bug Flags:
flashplayer-injection -
flashplayer-qrb +
flashplayer-bug -

Details

(Reporter)

Description

8 years ago
Problems:

- often, we update from tamarin-redux, rebase, then discover that we have imported something from a broken build, that will prevent a successful sandbox run.

- hygenic problems probably shouldn't break the build, but also tend to creep in unchecked.  (whitespace, being one).

- push triggers can run on a remote depot, but cannot prevent a push from happening.  so even if you have something a script can check, its not clear what it can do about it since it cannot prevent the push.

Proposal

- introduce a repository that only gets pushed to when the build system deems it okay.  tentatively: tamarin-redux-stable, and tentatively: only push to there when the acceptance phase passes.   maybe, a final step in the acceptance tests puhes to that repo

- devs can pull from there, to avoid importing bustage that might go unfixed for a half-day or a day.

- no pushes allowed directly from users (or, pushes allowed only with the -f flag).  we need to prevent goofs, but not be overly restrictive.

Risks

 - confusion over tamarin-redux-stable vs tamarin-central
 - automation gone amuck (automatic pushing is always a bit sketchy to me)
 - heavy handed:  would a "stable" tag do the trick, or just litter the repository with old tags and tag-updating changesets?

Updated

8 years ago
Flags: flashplayer-qrb+
Priority: -- → P3
Target Milestone: --- → flash10.2

Updated

7 years ago
Flags: flashplayer-injection-
Flags: flashplayer-bug-
Priority: P3 → --
Target Milestone: Q3 11 - Serrano → Future
You need to log in before you can comment on or make changes to this bug.