Closed Bug 272172 Opened 20 years ago Closed 20 years ago

Add readme to latest* directories explaining what's in them

Categories

(mozilla.org :: FTP: Staging, task)

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: bugzillamozilla, Assigned: chase)

References

()

Details

Attachments

(1 file)

Of the three nightly folders, two are clearly separated: /latest-trunk and
/latest-1.7 (branch). The third one, /latest, is just confusing and ambiguous.

Two possible solutions:

1. "Kill it" (to quote Asa, https://bugzilla.mozilla.org/show_bug.cgi?id=67445#c7)
-or-
2. Add some stub at the top of the folder that explains what it is ("!This
folder is link to latest-trunk")

Prog.
Assignee: mitchell → zach
Component: Miscellaneous → FTP: Staging
QA Contact: mitchell → myk
One potentially significant issue with this is that people and automated pulling
scripts expect builds to be in /mozilla/nightly/latest and any change will break
these existing systems. 
Replacing "latest" with "latest-trunk" in these automated scripts should be very
simple. All we have to do is document this change, and for this type of
audience, b.m.o should suffice.

Nevertheless, if you're really worried about the implications of removing this
folder, the second option still stands.

Prog.
replacing text in scripts that may never update and run on uncounted/unknown
boxes is nontrivial
So I guess that leaves us with the second option. I'm fine with it.

Prog.
We've discussed this several times in the past and decided against making either
of these changes. 
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
For the record, may I ask what was the rational in deciding against the second
option?

Thanks,

Prog.
Oh, a readme inside of each folder would be fine. Handing this to Chase. If he
cares about it, he can either do it or review any patches.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
Assignee: zach → cmp
Status: REOPENED → NEW
QA Contact: myk → zach
Summary: FTP: Remove /mozilla/nightly/latest → Add readme to latest* directories explaining what's in them
How about this one?

Prog.
Comment on attachment 168180 [details]
Draft README file for /latest

Who do I have to contact to get this in? Do readme files require reviews?

Prog.
I've added these suggested README files to mozilla/nightly/latest*.  Thanks for
offering them!
Status: NEW → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → FIXED
Verified. Thanks Chase for putting this in.

Prog.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: