Closed j-s-3 closed 5 years ago
Both mention of and table addition of 3.18 make me just a little ("minorly") squeamish, since we don't know if that's true til it happens. We do control it tho, so if no matter what it'll be 3.18, I believe you. Seems something you could just add later when sure tho (remove the 3.18 sentence, and table row, it's still the same PR IMO:P).
Q: Is it worth a note (now, or later if you buy into my last comment) that tickets should be filed in JIRA and the intent is this project be deprecated? Believe we had the same thing for S3; can't remember the order we did it in, but believe we got some issues in the S3 project after the fact.
Q: Is it worth a note (now, or later if you buy into my last comment) that tickets should be filed in JIRA and the intent is this project be deprecated? Believe we had the same thing for S3; can't remember the order we did it in, but believe we got some issues in the S3 project after the fact.
Still +1 if needed, thanks for updating=)
Differences section and table update still seems useful to me?
@joedragons @bhamail @DarthHater I've updated this PR to reflect the 3.17 release.
Any intention to moveover and disables "Issues" in this project once we go live?
Cool! (maybe track "component records" as new GitHub issue?)
https://github.com/sonatype-nexus-community/nexus-repository-apt/issues/118
Any intention to moveover and disables "Issues" in this project once we go live?
@joedragons I think that is a decision for @bhamail and @DarthHater.
3.17 will include the apt plugin natively.