accumulo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Busbey <>
Subject Re: [git] Documentation and Plan of Action
Date Tue, 11 Jun 2013 11:16:49 GMT
Release Guide:

On Mon, Jun 10, 2013 at 10:44 PM, Josh Elser <> wrote:

> Alright, I think I covered all of the content that's needed.
> Disclaimer, I actually got Christopher to say "it's kind of long...". Yes,
> this was intended. I'd rather be (painfully) explicit front and lift out a
> TL;DR version from the master document.
> _Please_ give feedback now as to what is still unclear about after reading
> the document. I'd hate to have wasted all of this time writing this to just
> change our minds again in the near future
> Also, please look for text in _emphasis_ as these are things which I do
> not believe were decided upon as a group. Copied here for your ease:
> 1. Need to ensure that deleting remote branches is not an issue. History
> is still intact so this should not grind against ASF policy.
> 2. Do we have a nice write-up of the release policies?
> And, the last thing:
> Is everyone ok with the default branch when cloning the repository being
> latest unstable branch (synonymous with what "trunk" is now)? If so, is
> everyone ok with naming it `master`? This is what my vote is towards.
> Once we get these questions answered and the process reviewed, I believe
> we're ready to move forward with the INFRA ticket.
> - Josh
> On 06/05/2013 09:58 PM, Josh Elser wrote:
>> For those who are interested:
>> Fork of CMS site:**
>> asf/accumulo/site/branches/**git/<>
>> Active copy:**elserj/git/git.html<>
>> Jira issue:**jira/browse/ACCUMULO-1498<>
>> I finished a first draft of all but what should be done with Git
>> during/after a release (outlining RC tags, a final tag and cleanup for the
>> branch which started said work, with corresponding merges upstream).
>> Again, any and all help, preferably the form of patchs :D, is welcome,
>> but comments on ACCUMULO-1498 are the next-best thing. I tried to leave
>> placeholders on the site for information which needs to finalized by the
>> devs.
>> On 06/04/2013 11:04 PM, Josh Elser wrote:
>>> In an effort to track the abundance of information that we need to
>>> define, manage, etc before making the development switch to git, I've
>>> started a WIP document.
>>> Not all of the information included (perhaps "planned to be included" at
>>> this point) in the document is likely candidate for final inclusion in the
>>> site (e.g. steps to contact INFRA, getting github mirrors, etc); however, I
>>> like writing in markdown and this gave me a template without having to do
>>> other lifting of my own.
>>> If people want to contribute, I'm more than happy to put something up in
>>> /accumulo/contrib so that multiple people can directly add/modify
>>> information.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message