You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@archiva.apache.org by Olivier Lamy <ol...@apache.org> on 2012/07/10 12:38:30 UTC
1.4-M3 Release ?
Hi,
I'd like to start the release process for a 1.4-M3 (including the new UI !!).
Any objections ?
I will start that around end of july (need vacations first :-) ). (yes
Brett French folks has a lot :P ).
As this release will need to release a LOT of stuff (redback
core/components now imported in asf scm), I wonder what is the best
strategy:
* release redback components then call a vote, release redback core
then call a vote, release archiva then call a vote.
* release everything in one block then call a vote
Perso I prefer 2nd mode (can be faster)
Ideas ?
Thanks
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: 1.4-M3 Release ?
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1
Have great vacations ;)
Regards
JB
On 07/10/2012 02:47 PM, Brett Porter wrote:
>
> On 10/07/2012, at 3:38 AM, Olivier Lamy wrote:
>
>> Hi,
>> I'd like to start the release process for a 1.4-M3 (including the new UI !!).
>> Any objections ?
>
> Great!
>
>> I will start that around end of july (need vacations first :-) ). (yes
>> Brett French folks has a lot :P ).
>
> :D
>
>>
>> As this release will need to release a LOT of stuff (redback
>> core/components now imported in asf scm), I wonder what is the best
>> strategy:
>> * release redback components then call a vote, release redback core
>> then call a vote, release archiva then call a vote.
>> * release everything in one block then call a vote
>>
>> Perso I prefer 2nd mode (can be faster)
>
> I think that makes sense. Do the components need to be separate releases, or should they just be folded in as 1.4-M3-SNAPSHOT as well since they are under the Archiva group?
>
> Also, should the relevant parts of the red back site be folded into Archiva's?
>
> - Brett
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: 1.4-M3 Release ?
Posted by Deng Ching <oc...@apache.org>.
On Tue, Jul 10, 2012 at 9:21 PM, Brett Porter <br...@apache.org> wrote:
>
> On 10/07/2012, at 6:00 AM, Olivier Lamy wrote:
>
> >>
> >> I think that makes sense. Do the components need to be separate
> releases, or should they just be folded in as 1.4-M3-SNAPSHOT as well since
> they are under the Archiva group?
> > currently:
> > * redback core has groupId: org.apache.archiva.redback
> > * redback components: org.apache.archiva.redback.components
> >
> > You mean only one tree of sources ?
> > http://svn.apache.org/repos/asf/archiva/trunk/
> >
> > /redback-components
> >
> /redback-core
> > ?
> >
> > Yup that could ease the release but we will release everything all the
> > time and increase build time.
>
> Good point. Maybe ok to be separate for now, but over time I anticipate
> we'd fold it in / trim it out… my other concern was to make sure it's not
> too hard for contributors to build Archiva.
>
> >
> >>
> >> Also, should the relevant parts of the red back site be folded into
> Archiva's?
> > I have started some stuff:
> > * core: http://archiva.apache.org/redback/
> > * components: http://archiva.apache.org/redback/components/
>
> I was thinking of folding in the important bits to:
> http://archiva.apache.org/docs/1.4-SNAPSHOT/adminguide/security.html
> and
> http://archiva.apache.org/ref/1.4-SNAPSHOT/
>
> Happy to work on that, just wondering if it's a good idea.
>
+1 to folding in at least the Redback configuration stuff to
/adminguide/security.html. For the development docs of Redback, maybe we
could just link to (or point devs/contributors to)
http://archiva.apache.org/redback/ and
http://archiva.apache.org/redback/components/ ?
+1 to releasing 1.4-M3 as well :)
Thanks,
Deng
Re: 1.4-M3 Release ?
Posted by Brett Porter <br...@apache.org>.
On 10/07/2012, at 6:00 AM, Olivier Lamy wrote:
>>
>> I think that makes sense. Do the components need to be separate releases, or should they just be folded in as 1.4-M3-SNAPSHOT as well since they are under the Archiva group?
> currently:
> * redback core has groupId: org.apache.archiva.redback
> * redback components: org.apache.archiva.redback.components
>
> You mean only one tree of sources ?
> http://svn.apache.org/repos/asf/archiva/trunk/
>
> /redback-components
> /redback-core
> ?
>
> Yup that could ease the release but we will release everything all the
> time and increase build time.
Good point. Maybe ok to be separate for now, but over time I anticipate we'd fold it in / trim it out… my other concern was to make sure it's not too hard for contributors to build Archiva.
>
>>
>> Also, should the relevant parts of the red back site be folded into Archiva's?
> I have started some stuff:
> * core: http://archiva.apache.org/redback/
> * components: http://archiva.apache.org/redback/components/
I was thinking of folding in the important bits to:
http://archiva.apache.org/docs/1.4-SNAPSHOT/adminguide/security.html
and
http://archiva.apache.org/ref/1.4-SNAPSHOT/
Happy to work on that, just wondering if it's a good idea.
- Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
Re: 1.4-M3 Release ?
Posted by Olivier Lamy <ol...@apache.org>.
2012/7/10 Brett Porter <br...@apache.org>:
>
> On 10/07/2012, at 3:38 AM, Olivier Lamy wrote:
>
>> Hi,
>> I'd like to start the release process for a 1.4-M3 (including the new UI !!).
>> Any objections ?
>
> Great!
>
>> I will start that around end of july (need vacations first :-) ). (yes
>> Brett French folks has a lot :P ).
>
> :D
>
>>
>> As this release will need to release a LOT of stuff (redback
>> core/components now imported in asf scm), I wonder what is the best
>> strategy:
>> * release redback components then call a vote, release redback core
>> then call a vote, release archiva then call a vote.
>> * release everything in one block then call a vote
>>
>> Perso I prefer 2nd mode (can be faster)
>
> I think that makes sense. Do the components need to be separate releases, or should they just be folded in as 1.4-M3-SNAPSHOT as well since they are under the Archiva group?
currently:
* redback core has groupId: org.apache.archiva.redback
* redback components: org.apache.archiva.redback.components
You mean only one tree of sources ?
http://svn.apache.org/repos/asf/archiva/trunk/
/redback-components
/redback-core
?
Yup that could ease the release but we will release everything all the
time and increase build time.
>
> Also, should the relevant parts of the red back site be folded into Archiva's?
I have started some stuff:
* core: http://archiva.apache.org/redback/
* components: http://archiva.apache.org/redback/components/
>
> - Brett
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: 1.4-M3 Release ?
Posted by Brett Porter <br...@apache.org>.
On 10/07/2012, at 3:38 AM, Olivier Lamy wrote:
> Hi,
> I'd like to start the release process for a 1.4-M3 (including the new UI !!).
> Any objections ?
Great!
> I will start that around end of july (need vacations first :-) ). (yes
> Brett French folks has a lot :P ).
:D
>
> As this release will need to release a LOT of stuff (redback
> core/components now imported in asf scm), I wonder what is the best
> strategy:
> * release redback components then call a vote, release redback core
> then call a vote, release archiva then call a vote.
> * release everything in one block then call a vote
>
> Perso I prefer 2nd mode (can be faster)
I think that makes sense. Do the components need to be separate releases, or should they just be folded in as 1.4-M3-SNAPSHOT as well since they are under the Archiva group?
Also, should the relevant parts of the red back site be folded into Archiva's?
- Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/