So we are talking about two kinds of binaries: the binary release and maven 
artifacts

The binary release can be built from the v0.1.0 tag, and I think there’s no 
reason not to provide it along with the source release.


S2GRAPH-115 is about the maven artifact.

Because with only some SBT setting changes it should be possible to make the 
binary artifacts that has the exactly same sources as in v0.1.0 and is 
compliant with the rules of ASF and the Maven Central, 

I was thinking of doing that for v0.1.0; if the rule is such that maven 
deployments should be possible and reproducible from the corresponding tag, 
Maven publishing may be only possible after v0.1.1.

Either way, I’ll work on making the SBT settings for S2GRAPH-115. Please advise 
as necessary, thanks.



JW



> On Oct 31, 2016, at 2:13 AM, Sergio Fernández <sergio.fernan...@redlink.co> 
> wrote:
> 
> (travelling with limited connectivity)
> 
> Guys, I guess 0.1.0-incubating would be just a source release. You can't
> modify the source that have been voted to release the Maven binary
> artifacts. Therefore that needs to be done in a new release, 0.1.1 if you
> just want to address the Maven packaging with no new features, 0.2.0 if you
> want to wait for new stuff.
> 
> BTW, repositoy.apache.org is synced with Maven Central. You should have
> access with you ASF accounts, so you can start to push snapshots there
> whenever the issue is fixed.
> 
> On Oct 30, 2016 07:30, "Jong Wook Kim" <jongw...@nyu.edu> wrote:
> 
>> S2GRAPH-115 is for the maven central upload, which is a separate problem
>> with the binary release
>> 
>> The binary release is what we make using ‘sbt package’, which should make
>> easier for the first-time users to download and try out S2Graph; so I
>> thought it would be nice to put this along with the announcement.
>> 
>> Anyone can run ‘sbt package’, and it should be good to go, preferably
>> after some testing on various OSX/linux platforms.
>> 
>> BTW, as per S2GRAPH-115, I’m still figuring out how to do a Maven Central
>> upload, any clarification would be appreciated.
>> 
>> JW
>> 
>>> On Oct 30, 2016, at 1:29 AM, DO YUNG YOON <sho...@gmail.com> wrote:
>>> 
>>> I just uploaded RC6 into
>>> https://dist.apache.org/repos/dist/release/incubator/s2graph/
>>> I guess we need one day waiting while mirrors set up.
>>> 
>>> @JW.
>>> 
>>> I created tag 'v0.1.0-incubating', and removed RC tags.
>>> 
>>> Depends on if how we are going to release binary to asf nexus, I think we
>>> need to change build.sbt so did not changed version in build.sbt yet.
>>> 
>>> Regarding to binary release, can anyone(I think JW is already helping
>> out)
>>> help me figure out how to resolve S2GRAPH-115 ?
>>> 
>>> One last question is should we announce 0.1.0 release or wait until
>> binary
>>> goes to asf nexus?
>>> 
>>> Thanks.
>>> DOYUNG YOON
>>> 
>>> On Sat, Oct 29, 2016 at 3:28 PM Jong Wook Kim <jongw...@nyu.edu> wrote:
>>> 
>>> Hi,
>>> 
>>> I don’t think any further actions happened since the passing vote email.
>>> 
>>> So what comes in my mind for the next steps are:
>>> 
>>> - tag v0.1.0 and remove the RC tags
>>> - update the version in build.sbt to 0.1.1-SNAPSHOT
>>> - upload the source release to ASF mirrors, and the binary release as
>> well,
>>> if possible. - the instructions are here <
>>> http://incubator.apache.org/guides/releasemanagement.html#
>> understanding-distribution
>>>> 
>>> - publish the binary and source JAR to the Maven Central.
>>> - announce the release and post the download links to mailing lists, at
>> the
>>> s2graph website, etc.
>>> 
>>> As for the Maven Central release, we have S2GRAPH-115 <
>>> https://issues.apache.org/jira/browse/S2GRAPH-115> open for doing that,
>> and
>>> I have a few questions (@sergio):
>>> 
>>> - I saw these instructions <
>>> http://incubator.apache.org/guides/release-java.html>, which are largely
>>> incomplete. We need to know how to get access for using
>> org.apache.s2graph
>>> groupId. Do we need to file a ticket to Sonatype OSSRH <
>>> http://central.sonatype.org/pages/ossrh-guide.html>, or does ASF have a
>>> separate mechanism for Maven Central publishing?
>>> - What are the rules that the POMs and JARs should strictly follow? ASF’s
>>> instruction <
>>> http://incubator.apache.org/guides/release-java.html#jar-manifest> page
>> is
>>> just full of TODOs and doesn’t look very authoritative.
>>> 
>>> Thanks,
>>> JW
>>> 
>>> 
>>> 
>>>> On Oct 27, 2016, at 9:23 AM, Sergio Fernández <wik...@apache.org>
>> wrote:
>>>> 
>>>> Do Yung, have you check the release has been already mirrored?
>>>> 
>>>> Then it's time for announce it:
>>>> 
>>>> * Minimum it should go to the mailing lists (dev@s2graph,
>>> general@incubator,
>>>> announce@apache); it's a good opportunity to reach a broader audience,
>> so
>>>> follow the example by others:
>>>> https://lists.apache.org/list.html?annou...@apache.org
>>>> 
>>>> * Also spread the work in Twitter or whatever creates some traction.
>>>> 
>>>> Thanks.
>>>> 
>>>> 
>>>> On Tue, Oct 25, 2016 at 8:44 AM, Sergio Fernández <wik...@apache.org>
>>> wrote:
>>>> 
>>>>> Good work, guys!
>>>>> 
>>>>> Finally did you push binary maven artifacts to asf nexus? In that case
>>>>> wait until they get mirrored http://search.maven.
>>>>> org/#search%7Cga%7C1%7Cs2graph before doing the official announcement.
>>>>> 
>>>>> On Tue, Oct 25, 2016 at 4:56 AM, DO YUNG YOON <sho...@gmail.com>
>> wrote:
>>>>> 
>>>>>> The vote for releasing Apache S2Graph 0.1.0-incubating passed with 3
>>>>>> binding +1s, 4 non-binding +1s, and no 0 or -1.
>>>>>> 
>>>>>> Binding +1s:
>>>>>> Justin Mclean
>>>>>> Sergio Fernández
>>>>>> Michael Stack
>>>>>> 
>>>>>> Thanks to everyone that tested our release and voted.
>>>>>> 
>>>>>> DOYUNG YOON
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Sergio Fernández
>>>>> Partner Technology Manager
>>>>> Redlink GmbH
>>>>> m: +43 6602747925 <+43%20660%202747925>
>>>>> e: sergio.fernan...@redlink.co
>>>>> w: http://redlink.co
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Sergio Fernández
>>>> Partner Technology Manager
>>>> Redlink GmbH
>>>> m: +43 6602747925 <+43%20660%202747925>
>>>> e: sergio.fernan...@redlink.co
>>>> w: http://redlink.co
>> 
>> 

Reply via email to