On 3/5/12 10:29 PM, Bongjae Chang wrote:
> Hi Ryan,
>
> Thank you for quick reply.
>
> I'd appreciate if you setup nightly jobs.
They should run tonight.
Added thrift and memcached components to our jira with you as the lead.
Added thrift-1.0 and memcached-1.0 as versions. Can add additional versions
as needed.
>
> For performing releases, perhaps could you inform any guides to me?
Prerequisite: Please read [1] for details on setting up pgp.
1. Prepare the release:
'mvn release:clean release:prepare'
answer the questions the plugin asks (i.e., release version, next
development version, etc).
When the build starts, there will be a point where it pauses and prints
a *. The line above
should be something about the pgp password. Enter the password for your
pgp key.
2. Perform the release:
Assuming all went well with step 2, perform the following steps:
'mvn -DconnectionUrl=scm:git:file://[path to local repo] release:perform'
The [path to local repo] should refer to your local copy and not the
remote since your local copy
will have the tags (remember, changes aren't pushed).
Pgp password will be asked for again.
3. Once the release is done, follow the instructions for "Release It" [2].
4. If no errors flagged when releasing the bits via nexus, push the
changes generated
by the release plugin to your repository. Make sure to push the
new tag as well
(git push --tags).
If there were problems, you can reset the head of your local
repository to the commit
prior to the commits generated by the release plugin, correct the
issue, and repeat
the steps above.
[1]
https://docs.sonatype.org/display/Repository/How+To+Generate+PGP+Signatures+With+Maven
[2]
http://java.net/projects/maven2-repository/pages/MigrationAndCleanupRelatedDocumentation#Release_It!
>
> Thanks.
>
> Regards,
> Bongjae Chang
>
>
>
>
> On 3/6/12 1:11 PM, "Ryan Lubke"<ryan.lubke_at_oracle.com> wrote:
>
>> On 3/5/12 7:00 PM, Bongjae Chang wrote:
>>> Hi Ryan,
>>>
>>> Thank you so much for your work!
>>>
>>> And I have some questions.
>>>
>>> 1. Will the uploading cycle of grizzly-memcached and grizzly-thrift's
>>> snapshot be maintained as it was before? (Will they need a manual push
>>> by
>>> someone or will they be published nightly automatically?)
>> I can setup nightly jobs for thrift and memcached (later tonight or
>> tomorrow).
>>> 2. If I think it can be released as not 1.0-SNAPSHOT but 1.0, should I
>>> just inform you about that? Then will you release them and push(upload)
>>> release-binaries to repositories(http://repo1.maven.org or
>>> https://maven.java.net/content/repositories/snapshots)?
>> Since you have commit privileges, you should be able to perform releases
>> for thrift/memcached when you see fit. That said, I'm sure either of us
>> would
>> be happy to help.
>>> 3. I think it will be great if any guides or links are published at the
>>> grizzly web pages for someone's contacting sources which are related to
>>> grizzly project because they have different repositories from grizzly.
>>> Currently, only grizzly sources are guided as the following link.
>>>
>>> http://java.net/projects/grizzly/sources/git/show
>>> http://grizzly.java.net/nonav/docs/docbkx2.2/html/sourcecode.html
>> Sure, we can do that.
>>
>> We could go further and create java.net projects for thrift and
>> memcached and then make them subprojects
>> of grizzly. This would give you different issue trackers/mailing
>> lists. Your call there. I'm happy updating our site and adding jira
>> categories for you.
>>> Here is the reference link.
>>>
>>> http://www.jboss.org/netty/related-projects
>>>
>>> It is publishing related projects such as Protobuf, Tools(thrift), play
>>> framework and etc...
>>>
>>> I would like to know your thoughts. :)
>>>
>>> Thanks!
>>>
>>>
>>> Regards,
>>> Bongjae Chang
>>>
>>>
>>>
>>>
>>> On 3/6/12 8:42 AM, "Ryan Lubke"<ryan.lubke_at_oracle.com> wrote:
>>>
>>>> I've moved thrift and memcached to their own repositories (keeps
>>>> branching/tagging clear vs sharing):
>>>>
>>>> - grizzly~thrift
>>>> - grizzly~memcached
>>>>
>>>> Versions are set to 1.0-SNAPSHOT. They are all yours, Bongjae :)
>>>>
>>>> On 2/20/12 6:20 PM, Bongjae Chang wrote:
>>>>> Hi Ryan and Alexey,
>>>>>
>>>>> I agreed with your opinions. And I would like to follow your
>>>>> decisions.
>>>>>
>>>>> Thanks.
>>>>>
>>>>> PS) Maybe it seems that GrizzlyMemcached is just completed. Zookeeper
>>>>> integration was the last work which I had planned. :-)
>>>>>
>>>>> Regards,
>>>>> Bongjae Chang
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On 2/21/12 8:33 AM, "Ryan Lubke"<ryan.lubke_at_oracle.com> wrote:
>>>>>
>>>>>> On 2/20/12 2:55 PM, Oleksiy Stashok wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>>> Bongjae's commits this weekend gave me pause about the proper place
>>>>>>>> for these projects.
>>>>>>>>
>>>>>>>> 1) Core Grizzly's branching cycles will differ from how these
>>>>>>>> projects would typically evolve.
>>>>>>>> For example, Bonjae's recent commits (no fault of his own)
>>>>>>>> were
>>>>>>>> made in the current master
>>>>>>>> which is for 2.3, but these same commits are relevant for
>>>>>>>> 2.2.
>>>>>>>> 2) In most cases (please let me know if you disagree), there won't
>>>>>>>> need to be core framework
>>>>>>>> changes for these particular projects to evolve.
>>>>>>>> 3) Core release cycle is going to differ. If memcached isn't
>>>>>>>> ready,
>>>>>>>> we don't want to hold up
>>>>>>>> the core release for it, nor do we want to perform a release
>>>>>>>> that pushes final versions of
>>>>>>>> these artifacts to maven when they aren't ready for prime
>>>>>>>> time.
>>>>>>>>
>>>>>>>> I'd like to propose creating two new repositories (one for thrift
>>>>>>>> and
>>>>>>>> the other for memcached)
>>>>>>>> and move the existing code there. Bonjgae can release 1.0 versions
>>>>>>>> (or whatever version he feels
>>>>>>>> is correct) when he feels they are properly baked depending on
>>>>>>>> whatever final version of Grizzly
>>>>>>>> is available within Maven.
>>>>>>>>
>>>>>>>> Thoughts? Comments?
>>>>>>> May be we can create just one repository for grizzly contributions
>>>>>>> like memcached, thrift, potentially protobufs etc?
>>>>>> As long as each 'project' is maintained separate, it should be fine.
>>>>>>> Thanks.
>>>>>>>
>>>>>>> WBR,
>>>>>>> Alexey.
>>>>>>>
>