Okay, I've updated the DOAP to match the SVN dist upload date (svn commit timestamp), and added the missing entries. I then manually updated all the entries in JIRA to reflect the same dates, and did a sync on reporter.apache.org (which is still a day-off... waiting for feedback on that from ComDev list).
On Wed, Sep 7, 2016 at 11:06 AM Christopher <[email protected]> wrote: > Okay, SVN dist date is easy enough to check, based on SVN commit > timestamps. I'll converge on those. I'm not so concerned about precision as > I am about consistency, especially to inform the filling in of the gaps. > > On Wed, Sep 7, 2016 at 10:49 AM Sean Busbey <[email protected]> wrote: > >> I agree with Billie that the technically-correct-ASF-policy-date is >> the SVN dist date. Similar to Josh I don't think this is a place where >> we need a lot of precision and anything within a week or two is good >> enough. >> >> On Tue, Sep 6, 2016 at 6:36 PM, Christopher <[email protected]> wrote: >> > I noticed that there were a few missing releases in our DOAP file, and I >> > also noticed lots of discrepancies between what's in JIRA as the release >> > date, when the tag was created, when the announcement was made (and on >> > which list), what the date was in reporter.apache.org, and what the >> date >> > was in DOAP. >> > >> > There are 3 places we record the "official" release date: >> > * doap_Accumulo.rdf >> > * JIRA >> > * reporter.apache.org >> > >> > Reporter actually has a sync-to-JIRA feature (but it's off-by-one... I'm >> > investigating that), and I'd like to just use that feature rather than >> try >> > to manually keep things sync'd up there also, so that leaves just 2 >> places >> > to update. >> > >> > There are several sources we can use for the "official" release date: >> > * SCM tag date >> > * Date uploaded to SVN dist >> > * Announce email date >> > * Vote date >> > >> > I don't like using the vote date, because that doesn't say when the >> release >> > occurred, just when we agreed on what will comprise the release. SVN >> dist >> > might technically be the best date to use, but it's a pain to track that >> > down, and it typically precedes the announcement by at least 24 hours. I >> > think I like announce date the best, but we actually forgot to announce >> on >> > at least one occasion, and we sometimes announce on different lists >> (dev@ >> > user@ announce@). >> > >> > Even if they are wrong, I'd like to sync up these different locations, >> so >> > they don't show different dates for a release... and I'd like to decide >> on >> > a standard from now on, so we know what a date means, and it doesn't >> vary >> > so much. >> >> >> >> -- >> busbey >> >
