11 Feb
2016
11 Feb
'16
4:44 p.m.
Some notes:
- if the developer already did PRs somehow other committers were notified
about changed in the app. I don't see how the 24 h would help somehow,
since reviewing should be done based on issues and not releases;
- there are many apps on e.x.o (around 800). Sending [ANN] for XE is doable
since they are big releases and usually take around 3 months of
development. But having ANN mails for every bugfix release on contrib app
IMO is an overkill.
Thanks,
Caty
On Thu, Feb 11, 2016 at 1:51 PM, vincent(a)massol.net <vincent(a)massol.net>
wrote:
On 11 Feb 2016 at 12:02:45, vincent(a)massol.net (vincent(a)massol.net(mailto:
vincent(a)massol.net)) wrote:
Hi devs,
I’d like to conclude this discussion (so far only Edy, Caty and myself
have
expressed an opinion and we need more opinions).
I’d also like to modify it a bit, as follows:
I’d like to propose to add some guidelines to contrib.xwiki.org when a
committer
of xwiki-contrib wants to release an extension:
* Always send a Proposal mail to the devs list, announcing the wish to
perform a
release, with the following information:
** A jira link to the fixed issues that will be
in that release
** The version id that will be released
* Wait for at least 24 hours to let others the time to review some
commits, test
the extension, verify the list of issues, provides comments,
etc. This is also important so that the project lead can talk to the
committer wishing to perform the release if he wants to (to sync on stuff
planned, etc).
* Before the release is done, release the version
in JIRA and create the
next version (so that future work can be planned). If the
committer doesn’t
have access, ask for help on IRC or in the mail proposal mail.
* Before the release is done, integrate translations from l10n (if any).
Thanks
-Vincent
* Once the release is performed, update the
documentation on xwiki.org(
http://xwiki.org) (including the release notes
section)
* Send an [ANN] mail on the users list to
announce the release, with a
link to the page on e.x.o and to the Release Notes on
e.x.o
Some notes:
* This process is really lightweight and for example much simpler than
the one at
the ASF (they require a vote, waiting for longer, etc).
* I don’t feel we can reduce the wait time to
less than 24 hours. It’s
already very very short for the community to be able to
react (not everyone
is working on xwiki full time!).
* Compared from the previous proposal this allows
any committer to
perform a release and not have to wait on the lead to be
available, while
at the same time allowing some time for the lead to react if need be
(although I agree that 24 hours is quite short. However in case of mistakes
it should be easy to re-release a new version quickly too).
* The idea of this revised proposal is to try to
make extensions
releases more fluid.
WDYT?
Thanks
-Vincent
On 9 Jul 2015 at 11:11:57, vincent(a)massol.net (vincent(a)massol.net
(mailto:vincent@massol.net)) wrote:
> Hi devs,
>
> I’d like to propose to add some guidelines to contrib.xwiki.org when
someone
wants to release a project, especially when that person is not the
project lead.
>
> * The person wanting to do the release should contact the project
lead,
preferable either through IRC or the mailing list to mention its
intent to perform a new release.
> ** This allows anyone who also want to have
some issue fixed be able
to do so in the same release for example.
> ** Usually that person will not have the
permission to create a
version in JIRA for that project and thus he/she’ll need the
Project Lead’s
help for that
>
> WDYT?
>
> Thanks
> -Vincent
>
>
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs