On 22 Jun 2009, at 19:14, Vincent Siveton wrote:
Hi folks,
Since the 1.0 release is now out, we need to prepare 1.1!
During this first release, a couple of things are pointed:
- we did a *lot* of changes in poms/assemblies to be ASF compliant. We
need to port them to the trunk. I am willing to help and probably Ian
can jump it. The first of them is to add "incubating" in the
artifact's names. Do you see other specific things?
I have a git merge in process to create a modified trunk and a patch
set that could be applied to the current trunk.
It will be easier to do this if there isn't too much movement in the
structure of branches.
Unfortunately, although the merge completed in about a minute (slow
for git) the merge is hitting almost every file in the source tree, so
I am going to have to go through and cherry pick individual commits in
order.
or
We could just work out what we did, and redo the work in trunk... but
I would prefer to cherry pick.
- do we need to release both java and PHP impl together [1] in the
future?
IMHO, the actual release process was quick to execute, so if they are
done together, I think its almost optimized.
The last one took about 30 minutes end to end, on a reasonable
connection.
The bit that was really slow was the voting.
If not, what are your plans?
- others?
Also, I propose to create a svn externals to manage the branch, ie
\shindig\trunks pointing to both 1.0 (branch) and 1.1 (trunk) and also
site/sandbox
Since we have now a website, I think the final layout could be
\shindig\site (moved for /trunk/site)
\shindig\trunk
\shindig\trunks (new)
\shindig\branches
\shindig\sandbox
If no objection, I will process in 72h.
Is this going to make the merge harder ?
Cheers,
Vincent
[1] http://shindig-dev.markmail.org/message/hu3k5mwrrgcx5hrd
