Re: [DISCUSSION] Apache NetBeans 16-u1 Finalization Steps

2023-02-27 Thread Neil C Smith
On Wed, 4 Jan 2023 at 02:13, Laszlo Kishalmi  wrote:
> Created files updates-16.xml and updates-16-u1.xml (and gz and sha512 in
> the same pattern). updates.xml and others have been replaced with
> symlinks pointing to the 16-u1 versions.

Now updated again to point to the archived versions, as part of
archiving NetBeans 16.  All seems to still be working correctly .. for
anyone who has a drastic need to run 16 again! :-)

Let me know if you see any problems.

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





Re: [DISCUSSION] Apache NetBeans 16-u1 Finalization Steps

2023-01-08 Thread Eric Bresie
Kind of OBE by now but maybe this might have helped some (and the links on
the page)
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Release+Management

Eric Bresie
ebre...@gmail.com


On Tue, Jan 3, 2023 at 8:13 PM Laszlo Kishalmi 
wrote:

>
> On 1/3/23 02:33, Neil C Smith wrote:
> > Hi Laszlo,
> >
> > On Mon, 2 Jan 2023 at 20:59, Laszlo Kishalmi 
> wrote:
> >> I've started the finalization steps for Apache NetBeans 16-u1 release.
> > Thanks for leading this through, and sorry for being personally
> > incommunicado and not getting around to voting - I would love to claim
> > excessive merriment, but mainly just laid low by a virus. :-\
>
> Get well, that's the important!
>
> I have not felt myself alone in this release, thank you for guiding me
> through! It seems we've evolved quite much, since my days.
>
>
> >> So far:
> >>
> >>- Created a "16-u1" tag in Git
> >>- Moved the 16-u1 folder into the release area in subversion.
> > Sounds good.
> >
> >> Next, I'd do the following:
> >>
> >>- do a subversion copy on ^/release/netbeans/netbeans/16-u1/nbms as
> >> ^/release/netbeans/netbeans/16/nbms/16-u1
> > No need for that.  Just keep everything where it is.  We don't want
> > duplicate binaries in the releases section, and keeping things clearly
> > separated is better (in some ways) for managing.
> >
> >>- Prepare a manually patched updates.xml (the gz as well) on the
> >> NetBeans VM adding the new location of the two patched modules.
> >>- Wait a day for the mirrors to be sync-ed
> > No need for that - no mirrors to sync anymore!  There is instead a
> > download CDN service - dlcdn.a.o
> >
> > If you check the .htaccess file on the VM, you'll notice we no longer
> > link to closer.lua but directly to dlcdn.  The main download pages
> > still use closer.cgi, but you should see the link come up as dlcdn in
> > most cases - eg.
> >
> https://www.apache.org/dyn/closer.cgi/netbeans/netbeans/16/netbeans-16-bin.zip
> >
> > So, to make this easier, please hardcode the links in updates.xml to
> >
> >
> https://dlcdn.apache.org/netbeans/netbeans/16-u1/nbms/extide/org-netbeans-modules-gradle.nbm
> >
> https://dlcdn.apache.org/netbeans/netbeans/16-u1/nbms/java/org-netbeans-modules-gradle-java.nbm
> >
> > Could do with a better system for this, as we'll need to update the
> > links again when we archive.  Perhaps using alternative relative links
> > and .htaccess.  I realise your suggestion to copy under 16/nbms/ might
> > help there, but other downsides to that.
> >
> >>- Activate the patched update.xml on NetBeans VM (Keeping a backup
> >> version)
> > Yes, please keep a backup in place.  Also make sure the owner /
> > permissions ensure it's not served.
> Well, I left the owner as www-data:www-data, the .htaccess takes care
> that only updates.xml* is served.
>
> Created files updates-16.xml and updates-16-u1.xml (and gz and sha512 in
> the same pattern). updates.xml and others have been replaced with
> symlinks pointing to the 16-u1 versions.
>
> It seems to be working, so people will start to receive these updates on
> the next update center check.
>
> I'm sending out announcements soon.
>
> Once again,
>
> Thank you Neil!
>
>
> >
> > And please use [RELEASES] in the email subject - helps anyone doing
> > subject filtering.
> >
> > Best wishes,
> >
> > Neil
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> > For additional commands, e-mail: dev-h...@netbeans.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: dev-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>


Re: [DISCUSSION] Apache NetBeans 16-u1 Finalization Steps

2023-01-03 Thread Laszlo Kishalmi



On 1/3/23 02:33, Neil C Smith wrote:

Hi Laszlo,

On Mon, 2 Jan 2023 at 20:59, Laszlo Kishalmi  wrote:

I've started the finalization steps for Apache NetBeans 16-u1 release.

Thanks for leading this through, and sorry for being personally
incommunicado and not getting around to voting - I would love to claim
excessive merriment, but mainly just laid low by a virus. :-\


Get well, that's the important!

I have not felt myself alone in this release, thank you for guiding me 
through! It seems we've evolved quite much, since my days.




So far:

   - Created a "16-u1" tag in Git
   - Moved the 16-u1 folder into the release area in subversion.

Sounds good.


Next, I'd do the following:

   - do a subversion copy on ^/release/netbeans/netbeans/16-u1/nbms as
^/release/netbeans/netbeans/16/nbms/16-u1

No need for that.  Just keep everything where it is.  We don't want
duplicate binaries in the releases section, and keeping things clearly
separated is better (in some ways) for managing.


   - Prepare a manually patched updates.xml (the gz as well) on the
NetBeans VM adding the new location of the two patched modules.
   - Wait a day for the mirrors to be sync-ed

No need for that - no mirrors to sync anymore!  There is instead a
download CDN service - dlcdn.a.o

If you check the .htaccess file on the VM, you'll notice we no longer
link to closer.lua but directly to dlcdn.  The main download pages
still use closer.cgi, but you should see the link come up as dlcdn in
most cases - eg.
https://www.apache.org/dyn/closer.cgi/netbeans/netbeans/16/netbeans-16-bin.zip

So, to make this easier, please hardcode the links in updates.xml to

https://dlcdn.apache.org/netbeans/netbeans/16-u1/nbms/extide/org-netbeans-modules-gradle.nbm
https://dlcdn.apache.org/netbeans/netbeans/16-u1/nbms/java/org-netbeans-modules-gradle-java.nbm

Could do with a better system for this, as we'll need to update the
links again when we archive.  Perhaps using alternative relative links
and .htaccess.  I realise your suggestion to copy under 16/nbms/ might
help there, but other downsides to that.


   - Activate the patched update.xml on NetBeans VM (Keeping a backup
version)

Yes, please keep a backup in place.  Also make sure the owner /
permissions ensure it's not served.
Well, I left the owner as www-data:www-data, the .htaccess takes care 
that only updates.xml* is served.


Created files updates-16.xml and updates-16-u1.xml (and gz and sha512 in 
the same pattern). updates.xml and others have been replaced with 
symlinks pointing to the 16-u1 versions.


It seems to be working, so people will start to receive these updates on 
the next update center check.


I'm sending out announcements soon.

Once again,

Thank you Neil!




And please use [RELEASES] in the email subject - helps anyone doing
subject filtering.

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





Re: [DISCUSSION] Apache NetBeans 16-u1 Finalization Steps

2023-01-03 Thread Neil C Smith
Hi Laszlo,

On Mon, 2 Jan 2023 at 20:59, Laszlo Kishalmi  wrote:
> I've started the finalization steps for Apache NetBeans 16-u1 release.

Thanks for leading this through, and sorry for being personally
incommunicado and not getting around to voting - I would love to claim
excessive merriment, but mainly just laid low by a virus. :-\

>
> So far:
>
>   - Created a "16-u1" tag in Git
>   - Moved the 16-u1 folder into the release area in subversion.

Sounds good.

> Next, I'd do the following:
>
>   - do a subversion copy on ^/release/netbeans/netbeans/16-u1/nbms as
> ^/release/netbeans/netbeans/16/nbms/16-u1

No need for that.  Just keep everything where it is.  We don't want
duplicate binaries in the releases section, and keeping things clearly
separated is better (in some ways) for managing.

>   - Prepare a manually patched updates.xml (the gz as well) on the
> NetBeans VM adding the new location of the two patched modules.
>   - Wait a day for the mirrors to be sync-ed

No need for that - no mirrors to sync anymore!  There is instead a
download CDN service - dlcdn.a.o

If you check the .htaccess file on the VM, you'll notice we no longer
link to closer.lua but directly to dlcdn.  The main download pages
still use closer.cgi, but you should see the link come up as dlcdn in
most cases - eg.
https://www.apache.org/dyn/closer.cgi/netbeans/netbeans/16/netbeans-16-bin.zip

So, to make this easier, please hardcode the links in updates.xml to

https://dlcdn.apache.org/netbeans/netbeans/16-u1/nbms/extide/org-netbeans-modules-gradle.nbm
https://dlcdn.apache.org/netbeans/netbeans/16-u1/nbms/java/org-netbeans-modules-gradle-java.nbm

Could do with a better system for this, as we'll need to update the
links again when we archive.  Perhaps using alternative relative links
and .htaccess.  I realise your suggestion to copy under 16/nbms/ might
help there, but other downsides to that.

>   - Activate the patched update.xml on NetBeans VM (Keeping a backup
> version)

Yes, please keep a backup in place.  Also make sure the owner /
permissions ensure it's not served.

And please use [RELEASES] in the email subject - helps anyone doing
subject filtering.

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





[DISCUSSION] Apache NetBeans 16-u1 Finalization Steps

2023-01-02 Thread Laszlo Kishalmi

Dear Release Team,

I've started the finalization steps for Apache NetBeans 16-u1 release.

So far:

 - Created a "16-u1" tag in Git
 - Moved the 16-u1 folder into the release area in subversion.

Next, I'd do the following:

 - do a subversion copy on ^/release/netbeans/netbeans/16-u1/nbms as 
^/release/netbeans/netbeans/16/nbms/16-u1
 - Prepare a manually patched updates.xml (the gz as well) on the 
NetBeans VM adding the new location of the two patched modules.

 - Wait a day for the mirrors to be sync-ed
 - Activate the patched update.xml on NetBeans VM (Keeping a backup 
version)


Would that be aligned with you?




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists