#100 Standard EOL dates should be enforced.
Closed 4 years ago Opened 4 years ago by ralph.

As discussed at Flock, we should start enforcing standard EOL dates for non-standard branches so that stuff doesn't roll EOL throughout the year.

For the beginning, let's pick November 1st and July 1st as the two standard required EOL dates.

Let's not allow people to override it for now to keep things simple, although we may need to allow non-standard EOL dates in the future as we all get more experience with this stuff.

fedrepo-req, fedrepo-req-admin, and fedrepo-req-branch will all need this check.

/cc @mattdm - does that sound good?


I'm going to offer the bikeshed of December 1st instead of November 1st, but otherwise, sounds great.

@mattdm can this be a written policy somewhere that I can link to when throwing an error?

@mattdm can this be a written policy somewhere that I can link to when throwing an error?

Module guidelines? Or something else?

@mattdm That seems like a good place for it.

PR #103 should address this.

Metadata Update from @mprahl:
- Issue assigned to mprahl

4 years ago

So, as I commented in #103: I'd suggest June 1 and December 1 to start with, so that there's 6 and 6 months rather than 7 and 5.
Also, why not use May 31 and October 31 to match up with the "ideal" Fedora release schedule?

So, as I commented in #103: I'd suggest June 1 and December 1 to start with, so that there's 6 and 6 months rather than 7 and 5.
Also, why not use May 31 and October 31 to match up with the "ideal" Fedora release schedule?

The Fedora release targets are "First Tuesday in May" and "Last Tuesday in October" (roughly), so I guess to be consistent, we could do "Four weeks after the first Tuesday in May" and "Four weeks after the last Tuesday in October", but that seems complicated.

Right, first of May, sorry.
So, how about at least the change to June 1 so it's 6-6 rather than 7-5 months?

OK - let's do June 1st and December 1st. This accommodates @mattdm's bikeshed with @puiterwijk's adjustment for consistency.

Metadata Update from @mprahl:
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata