5:30 p.m.
the blessed repo is a mirror of the history that was gone in the maven repository.
sometime it is possible to redo a tag in the dev repo when a tag is not good, it's
usually combined with nexus staging capability with a worflow like:
1/ release and tag in dev repo under tag FINAL and in Nexus as a staged repository
2/ something was wrong : drop staged repository / destroy FINAL tag in dev repo
3/ release (again) and tag in dev repo under FINAL (again) and in Nexus as staged
repository (again)
4/ ok it is good : promote in Nexus and push in blessed repository the FINAL tag
On Jul 20, 2011, at 12:07 AM, Boleslaw Dawidowicz wrote:
I think what matters is that the purpose of the "blessed"
or "release" repo is only to track history for released stuff. So it doesn't
actually affect community or any of core devs. It would be mostly a responsibility of
Julien and me (if we decide to go this way) to keep it in sync. So I don't think it is
worth to argue too much around this stuff.
The main thing to decide is around the dev repo - "https://github.com/gatein" -
who has push access and who needs to ask core devs for merge or pass pull request.
Additionally how we should handle commit history. Also I think that in natural way a lot
of dev will be happening in private forks anyway as this is "the git" way of
working. Just wanted to clarify this as from my previous email it may look as something
that we want to avoid. We don't want to develop different git workflow.
Bolek
On Jul 19, 2011, at 7:13 PM, Boleslaw Dawidowicz wrote:
> Hi
>
> We were recently brainstorming a bit with Julien around Git usage for GateIn and here
is a draft of the doc:
>
> https://docs.google.com/document/pub?id=1dp3QODiZDG3KbolnBsCkjZWwYtIvCaQv...
>
> I would like all of you to read it and comment.
>
> The main concern is around having two spaces in github. Let me clarify reasoning
about this part a bit. If you look at how Infinispan uses git:
>
>
https://docs.jboss.org/author/display/ISPN/Contributing+to+Infinispan#Con...
>
> you will notice that in the end there are few people acting as "Project
Admin" and everything goes via them as a pull request. This means that all
development is being performed in private clones and forks and only code in clean state
hits the repo. It also means that few people have a lot on their shoulders to handle pull
requests.
>
> Julien proposed to have common more open space at
"https://github.com/gatein". We would be able to collaborate more on common
branches. It would be also more easy to track all development work that is going on in the
project in one place. We would be able to also give push/pull access to guys from QA and
Support.
>
> Separately we would have something aka "blessed" repo
(https://github.com/gateinportal). Only few people have access there, and everytime we
tag, release we push clean code with clean history there. Community doesn't really
need to be aware of it and we don't need to advertise it too much. It is more also for
safety reasons as git allows destructive operations so when more people can push things
into "gatein" space we can end up with losing some important history there.
>
> Personally I still have a bit mixed feelings around this two places idea and thats
partly why I'm asking for feedback. I assume that we would like to commit directly
into "gatein" space repos for feature requests, bugs and etc. We would still use
private forks for prototyping, experimenting or dirty commits but it would be advised to
push things to gatein space on regular bases for other work.
>
> The goal is to prepare some kind of public doc like infinispan wiki.
>
> Bolek
> _______________________________________________
> gatein-dev mailing list
> gatein-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/gatein-dev
_______________________________________________
gatein-dev mailing list
gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev