On Tue, Aug 2, 2016 at 11:18 AM, Keith Turner <ke...@deenlo.com> wrote: > On Mon, Aug 1, 2016 at 9:36 AM, John D. Ament <johndam...@apache.org> wrote: >> I'm -1 until the website issues are resolved. >> >> - Make sure its clear that any existing releases are not apache endorsed. > > One interesting thing this discussion has highlighted that we didn't > realize was the following : > > 1. Releases of Fluo before moving to apache were made available via > the fluo-io/fluo repo on GH > 2. The GitHub projects fluo and fluo-recipes were transferred to the > apache org on GH from the fluo-io repo on GH. The downloads came > along for the ride when the transfer happened. > 3. Now the downloads[1] look like ASF artifacts (because they under > the apache GH org) to someone not familiar with this history and ASF > release practices. > > What should we do about this? Personally I would like to delete the > old artifacts[1] from GH after we have a 1.0.0-incubating release of > Fluo. Is it ok to leave them there for now and is it ok for > fluo.apache.org to link to them with a disclaimer?
We just updated the website, you may need to force refresh to see updates. It no longer[1] has links to the pre-Apache releases (they still exist on Github). Still need guidance on adding links w/ disclaimers to the pre-Apache releases. We still have the documentation for the pre-Apache releases on the website, but have added very prominent disclaimers (see [2][3][4] for examples). [1]: http://fluo.apache.org/download/ [2]: http://fluo.apache.org/docs/ [3]: http://fluo.apache.org/docs/pre-asf/ [4]: http://fluo.apache.org/docs/fluo/1.0.0-beta-2/prod-fluo-setup/ > > This will be something to look out for in the future when projects > transfer GH repos to Apache. > > [1]: https://github.com/apache/incubator-fluo/releases > >> - Make sure the website points to resources contained within the ASF, e.g. >> fluo-dev is a bit of an oddity same for zetten. >> - Make sure that io.fluo is either replaced, or has a ticket to be replaced >> within your pom files. Its still not clear to me why your parent declares >> dependencies on previously released artifacts and why those can't be >> bundled within the release. >> >> John >> >> On Sat, Jul 30, 2016 at 2:33 PM Christopher <ctubb...@apache.org> wrote: >> >>> io.fluo was the groupId for Fluo before it transitioned to incubation. This >>> parent POM references a previously released (prior to acceptance into >>> incubation) resources artifact under that identity, which contains >>> checkstyle and Eclipse code formatter rules which this project still uses >>> to apply consistent formatting and style checks to maven projects using >>> this parent POM. >>> >>> On Sat, Jul 30, 2016 at 2:24 PM John D. Ament <johndam...@apache.org> >>> wrote: >>> >>> > What is io.fluo and why does this depend on it? Sounds like a branding >>> > issue. >>> > >>> > On Jul 30, 2016 14:14, "Christopher" <ctubb...@apache.org> wrote: >>> > >>> > > In preparation for a 1.0.0-incubating release of Fluo, the Fluo team is >>> > > first separately releasing a parent POM. This release passed a PPMC >>> vote >>> > on >>> > > the Fluo dev@ list here: >>> > > >>> > > >>> > >>> https://lists.apache.org/thread.html/2f801cc81b7eab1f3438da23d8973626755a77e9038f80cce2b30ae9@%3Cdev.fluo.apache.org%3E >>> > > >>> > > Please consider the following candidate for Fluo Parent POM >>> 1-incubating. >>> > > >>> > > Git Commit: >>> > > (https://git-wip-us.apache.org/repos/asf/incubator-fluo.git) >>> > > e9ed4334dd4cc5df27def417f26d6d7362470cb8 >>> > > Branch: >>> > > fluo-parent-1-rc2 >>> > > >>> > > If this vote passes, a gpg-signed tag will be created using: >>> > > git tag -f -m 'Apache Fluo Parent POM 1-incubating' -s >>> > > rel/fluo-parent-1-incubating e9ed4334dd4cc5df27def417f26d6d7362470cb8 >>> > > >>> > > Staging repo: >>> > > https://repository.apache.org/content/repositories/orgapachefluo-1003 >>> > > Source (official release artifact): >>> > > >>> > > >>> > >>> https://repository.apache.org/content/repositories/orgapachefluo-1003/org/apache/fluo/fluo-parent/1-incubating/fluo-parent-1-incubating-source-release.tar.gz >>> > > (Append ".sha1", ".md5", or ".asc" to download the signature/hash for a >>> > > given artifact.) >>> > > >>> > > Signing key fingerprint is: 8CC4F8A2B29C2B040F2B835D6F0CDAE700B6899D >>> > > >>> > > Please vote one of: >>> > > [ ] +1 - I have verified and accept... >>> > > [ ] +0 - I have reservations, but not strong enough to vote against... >>> > > [ ] -1 - Because..., I do not accept... >>> > > ... these artifacts as the 1-incubating release of Apache Fluo Parent >>> > POM. >>> > > >>> > > This vote will end on Tue Aug 02 18:30:00 UTC 2016 >>> > > (Tue Aug 02 14:30:00 EDT 2016 / Tue Aug 02 11:30:00 PDT 2016) >>> > > >>> > > Thanks! >>> > > >>> > > P.S. Hint: download the whole staging repo with >>> > > wget -erobots=off -r -l inf -np -nH \ >>> > > >>> > https://repository.apache.org/content/repositories/orgapachefluo-1003/ >>> > > # note the trailing slash is needed >>> > > >>> > >>> --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
